АЯ
Спасибо, Рома!
Size: a a a
2019 November 22
RV
Ur welcome
АЯ
Попробовал загуглить, какие есть способы деплоя без SSH и как их реализовать.
В выдаче поисковика лишь посты о том, насколько крут SSH для деплоя, как это просто и быстро.
Ни одного поста о том, что этого лучше бы избегать.
Пробовал по-разному запросы писать, но все так же
В выдаче поисковика лишь посты о том, насколько крут SSH для деплоя, как это просто и быстро.
Ни одного поста о том, что этого лучше бы избегать.
Пробовал по-разному запросы писать, но все так же
АЯ
Может кто-нибудь статейку подсказать годную по этой теме?
VM
машины под автоскейлом?
VM
или независымые машины?
RV
Packer+Ansible ну и user-data
АЯ
Независимые машины.
VM
машины за балансиром?
АЯ
VM
поднимаем рядом новые (Packer+Ansible ну и user-data) , переключаем на них балансир
VM
но лучше это под автоскейл , и автоскейлом разруливать
VM
создаем новый конфиг (с измененным имаджем ) , в автоскейле увеличимам к-во нод в 2 раза , ждем пока все поднимуться , потом уменьшаем до обычного значения . автоскуйл оставит ноды с новой конфигурацией
SS
разве дефолтный автоскейлинг не оставляет самую старую виртуалку?
VM
по умолчанию там политика убивать самую старую ноду
VM
при желании ее можно переопределить
VM
Amazon EC2 Auto Scaling supports the following custom termination policies:
OldestInstance. Terminate the oldest instance in the group. This option is useful when you're upgrading the instances in the Auto Scaling group to a new EC2 instance type. You can gradually replace instances of the old type with instances of the new type.
NewestInstance. Terminate the newest instance in the group. This policy is useful when you're testing a new launch configuration but don't want to keep it in production.
OldestLaunchConfiguration. Terminate instances that have the oldest launch configuration. This policy is useful when you're updating a group and phasing out the instances from a previous configuration.
ClosestToNextInstanceHour. Terminate instances that are closest to the next billing hour. This policy helps you maximize the use of your instances that have an hourly charge.
Default. Terminate instances according to the default termination policy. This policy is useful when you have more than one scaling policy for the group.
OldestLaunchTemplate. Terminate instances that have the oldest launch template. With this policy, instances that use the noncurrent launch template are terminated first, followed by instances that use the oldest version of the current launch template. This policy is useful when you're updating a group and phasing out the instances from a previous configuration.
AllocationStrategy. Terminate instances in the Auto Scaling group to align the remaining instances to the allocation strategy for the type of instance that is terminating (either a Spot Instance or an On-Demand Instance). This policy is useful when your preferred instance types have changed. If the Spot allocation strategy is lowest-price, you can gradually rebalance the distribution of Spot Instances across your N lowest priced Spot pools. If the Spot allocation strategy is capacity-optimized, you can gradually rebalance the distribution of Spot Instances across Spot pools where there is more available Spot capacity. You can also gradually replace On-Demand Instances of a lower priority type with On-Demand Instances of a higher priority type.
OldestInstance. Terminate the oldest instance in the group. This option is useful when you're upgrading the instances in the Auto Scaling group to a new EC2 instance type. You can gradually replace instances of the old type with instances of the new type.
NewestInstance. Terminate the newest instance in the group. This policy is useful when you're testing a new launch configuration but don't want to keep it in production.
OldestLaunchConfiguration. Terminate instances that have the oldest launch configuration. This policy is useful when you're updating a group and phasing out the instances from a previous configuration.
ClosestToNextInstanceHour. Terminate instances that are closest to the next billing hour. This policy helps you maximize the use of your instances that have an hourly charge.
Default. Terminate instances according to the default termination policy. This policy is useful when you have more than one scaling policy for the group.
OldestLaunchTemplate. Terminate instances that have the oldest launch template. With this policy, instances that use the noncurrent launch template are terminated first, followed by instances that use the oldest version of the current launch template. This policy is useful when you're updating a group and phasing out the instances from a previous configuration.
AllocationStrategy. Terminate instances in the Auto Scaling group to align the remaining instances to the allocation strategy for the type of instance that is terminating (either a Spot Instance or an On-Demand Instance). This policy is useful when your preferred instance types have changed. If the Spot allocation strategy is lowest-price, you can gradually rebalance the distribution of Spot Instances across your N lowest priced Spot pools. If the Spot allocation strategy is capacity-optimized, you can gradually rebalance the distribution of Spot Instances across Spot pools where there is more available Spot capacity. You can also gradually replace On-Demand Instances of a lower priority type with On-Demand Instances of a higher priority type.
vk
проблемка будет если на старых нодах ещё есть активные сессии. Ждать и проверять пока количество сессий не сравняется с 0?
VM
лучше при создании группы ее поставить , ту которую надо
VM
а почему у тебя они станут 0 ?