Matt,
Thanks for noting this. My understanding of the problem is that we should
put openstack.yaml into a separate package build from fuel-web repository.
When a user installs fuel-upgrade package it requires openstack.yaml
package of necessary version to be also installed.
Another idea here is
Hi, Vladimir,
I like the initiative, just to add some steps:
10) patch to fuel-qa/ and jenkins jobs to change the workflow of upgrades tests,
11) clarification on how upgrade should be tested (against which
repositories and ISO images), how update of upgrade rpm should be
tested
12)
Vladimir,
I am fully support moving fuel-upgrade-system into repository of its own.
However, I'm not 100% sure how docker containers are going to appear on the
upgraded master node. Do we have public repository of Docker images
already? Or we are going to build them from scratch during the
Oleg,
All docker containers currently are distributed as rpm packages. A little
bit surprising, isn't it? But it works and we can easily deliver updates
using this old plain rpm based mechanism. The package in 6.1GA is called
fuel-docker-images-6.1.0-1.x86_64.rpm So, upgrade flow would be like
By the way, first step for this to happen is to move
stackforge/fuel-web/fuel_upgrade_system into a separate repository.
Fortunately, this directory is not the place where the code is continuously
changing (changes are rather seldom) and moving this project is going to
barely affect the whole
Vladimir,
Thank you, now it sounds concieving.
My understanding that at the moment all Docker images used by Fuel are
packaged in single RPM? Do you plan to split individual images into
separate RPMs?
Did you think about publishing those images to Dockerhub?
--
Best regards,
Oleg Gelbukh
On
Oleg,
Yes, you are right. At the moment all docker containers are packaged into a
single rpm package. Yes, it would be great to split them into several
one-by-one rpms, but it is not my current priority. I'll definitely think
of this when I'll be moving so called late packages (which depend on
Vladimir,
Good, thank you for extended answer.
--
Best regards,
Oleg Gelbukh
On Thu, Jul 16, 2015 at 3:30 PM, Vladimir Kozhukalov
vkozhuka...@mirantis.com wrote:
Oleg,
Yes, you are right. At the moment all docker containers are packaged into
a single rpm package. Yes, it would be great to
One item that will impact this separation is that fuel_upgrade
implicitly depends on the openstack.yaml release file from
fuel-nailgun. Without it, the upgrade process won't work. We should
refactor fuel-nailgun to implement this functionality on its own, but
then have fuel_upgrade call this
Hi,
Let's put openstack.yaml to package if it requires for master node upgrade.
Environment update part should be removed as it never reached production
state.
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Thu, Jul 16, 2015 at 8:07 AM, Matthew Mosesohn
10 matches
Mail list logo
