New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenStack Upgrade - Stein #50
Comments
Stein seems now unmainted. Why not upgrading to a more recent version like Ussuri or Victoria ? |
Stein is the stable version we target. Bigger the gap between two OpenStack version is, bigger the effort/risk is. |
I see the point about going one version at a time, but given that event when Stein lands it will be 5 versions behind... If OVH already has the next step in mind (to which version the next jump will be), maybe a new issue can be opened so at least we know what to expect. Note that this issue is now in Backlog, so Stein is not to be expected atleast untill Fall 2021? By then Wallaby should be out and Stein probably EOL. |
I see that BHS6 (vps) has been upgraded to Stein so I guess BHS public cloud will follow? |
This issue is now in the So... |
I would also be really interested in this. We are also facing issues with our API-Clients and Security Certificates. |
We as well could love an update on this issue. Especially on the question what / when the next update from Stein onward will follow, since it is expected to be EOL soon as well. |
Hi all, Here is the planning of our coming upgrades from Newton to Stein. Status | OpenStack Region | Detailed impact DONE | UK1 | https://public-cloud.status-ovhcloud.com/incidents/mltz6rv3fpt5 |
@JacquesMrz much apprichiate this list helps a lot! Do you happen to know the release schedule / current release of GRA9 as well? |
Hello, any update on the upgrade status? As per OVH support, we cannot update security groups until the upgrade is finished. |
Could you explain me why the region SBG5 which has been migrating to Stein cf (https://public-cloud.status-ovhcloud.com/incidents/82d1l1ktrs41) has still no security groups, no port security enable ?
When I try to set enable port_security, I got
|
Coucou @maxdelorme , Even if SBG5 is running on OpenStack Stein, we need to update openvswitch so you will be able to use Security Groups. |
Dear @JacquesMrz, do you have an ETA for the openvswitch update? |
@JacquesMrz Any news on this ? Lack of security group management is a pretty big deal. |
@JacquesMrz I confirm that not be able to use security group on OpenStack is a pretty big security issue ! |
according to this links upgrade to openvswitch is done on many regions The scheduled maintenance has been completed. The scheduled maintenance has been completed. The scheduled maintenance has been completed. |
I confirm that I can now set Security Groups on SBG5 region (enable security port before) and also that port_security_enabled is true by default |
I see that upgrade of GRA7 has been completed a few hours ago: https://public-cloud.status-ovhcloud.com/incidents/1s899p8kmt01. Is there a link to upgrade IaC / provisionning scripts to Stein? Will we need to explicitly define port for each instance (like defined in https://blog.ledez.net/computing/ovh-openstack-stein-port-security-with-terraform-en/)? |
Upgrade off all our OpenStack infrastructure from Newton to Stein version.
BHS1 - Done
The text was updated successfully, but these errors were encountered: