| 2017-05-19 07:28:40 |
Volodymyr Litovka |
bug |
|
|
added bug |
| 2017-05-19 07:29:15 |
Volodymyr Litovka |
description |
Dears,
Summary: I wasn't be able to create xenial-based custom image with Heat integration.
There are few bugs in two areas actually:
1) Documentation to Heat incorrectly describers procedure of creating custom image
2) Installation of Heat's agents don't work when creating Xenial-based custom image
==== Documentation ===
a) https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#custom-image-script says that
git clone https://git.openstack.org/openstack/diskimage-builder.git
is enough to launch diskimage-builder. That's wrong at the moment - just git'ing diskimage-builder's tree don't provide access to required executables, one need to install it (preferably in virtualenv) in the way like this :
$ virtualenv dib
$ source dib/bin/activate
$ git clone https://git.openstack.org/openstack/diskimage-builder
$ cd diskimage-builder
$ pip install -e .
and just then all next steps are possible:
git clone https://git.openstack.org/openstack/tripleo-image-elements.git
git clone https://git.openstack.org/openstack/heat-agents.git
[ ... ]
b) I guess, it makes sense to note there are different branches of tripleo-image-elements / heat-agents and one need to distinguish between them: master, stable/ocata or stable/newton, e.g.
git clone -b stable/ocata https://git.openstack.org/openstack/tripleo-image-elements.git
git clone -b stable/ocata https://git.openstack.org/openstack/heat-agents.git
c) to proper work of os-*-config tools, it's required to have dib-run-parts tool on host VM, which need to be added to BASE_ELEMENTS variable (last entry in the following row):
export BASE_ELEMENTS="ubuntu selinux-permissive dib-run-parts"
==== Code ====
Few fixes required to diskimage-builder's elements to work with Xenial distribution:
d) in Xenial, dib-run-parts tool resides in 'python-dib-utils' package, which need to be reflected in diskimage-builder/diskimage_builder/elements/dib-run-parts/package-installs.yaml instead of 'dib-utils' (see (c) above)
e) heat-config-notify (used for notifying Heat about changes on VM) require keystoneclient, so this package need to be added to heat-agents/heat-config/install.d/heat-config-source-install/50-heat-config-soure (last entry in the following row):
pip install python-heatclient python-zaqarclient python-keystoneclient
f) there is broken dependency in os-collect-config's systemd integration, which prevents it starting upon VM start/reboot. This can be fixed using the following change in tripleo-image-elements/elements/os-collect-config/install.d/os-collect-config-source-install/10-os-collect-config:
[Install]
WantedBy=cloud-init.target
instead of "WantedBy=multi-user.target"
After all these changes, I was be able to create and launch xenial-based custom image using diskimage-builder tool.
Hope this'll help. Thank you. |
Dears,
Summary: I wasn't be able to create xenial-based custom image with Heat integration.
There are few bugs in two areas actually:
1) Documentation to Heat incorrectly describers procedure of creating custom image
2) Installation of Heat's agents don't work when creating Xenial-based custom image
==== Documentation ===
a) https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#custom-image-script says that the following command
git clone https://git.openstack.org/openstack/diskimage-builder.git
is enough to launch diskimage-builder. That's wrong at the moment - just git'ing diskimage-builder's tree don't provide access to required executables, one need to install it (preferably in virtualenv) in the way like this :
$ virtualenv dib
$ source dib/bin/activate
$ git clone https://git.openstack.org/openstack/diskimage-builder
$ cd diskimage-builder
$ pip install -e .
and just then all next steps are possible:
git clone https://git.openstack.org/openstack/tripleo-image-elements.git
git clone https://git.openstack.org/openstack/heat-agents.git
[ ... ]
b) I guess, it makes sense to note there are different branches of tripleo-image-elements / heat-agents and one need to distinguish between them: master, stable/ocata or stable/newton, e.g.
git clone -b stable/ocata https://git.openstack.org/openstack/tripleo-image-elements.git
git clone -b stable/ocata https://git.openstack.org/openstack/heat-agents.git
c) to proper work of os-*-config tools, it's required to have dib-run-parts tool on host VM, which need to be added to BASE_ELEMENTS variable (last entry in the following row):
export BASE_ELEMENTS="ubuntu selinux-permissive dib-run-parts"
==== Code ====
Few fixes required to diskimage-builder's elements to work with Xenial distribution:
d) in Xenial, dib-run-parts tool resides in 'python-dib-utils' package, which need to be reflected in diskimage-builder/diskimage_builder/elements/dib-run-parts/package-installs.yaml instead of 'dib-utils' (see (c) above)
e) heat-config-notify (used for notifying Heat about changes on VM) require keystoneclient, so this package need to be added to heat-agents/heat-config/install.d/heat-config-source-install/50-heat-config-soure (last entry in the following row):
pip install python-heatclient python-zaqarclient python-keystoneclient
f) there is broken dependency in os-collect-config's systemd integration, which prevents it starting upon VM start/reboot. This can be fixed using the following change in tripleo-image-elements/elements/os-collect-config/install.d/os-collect-config-source-install/10-os-collect-config:
[Install]
WantedBy=cloud-init.target
instead of "WantedBy=multi-user.target"
After all these changes, I was be able to create and launch xenial-based custom image using diskimage-builder tool.
Hope this'll help. Thank you. |
|
| 2017-05-19 07:33:47 |
Volodymyr Litovka |
description |
Dears,
Summary: I wasn't be able to create xenial-based custom image with Heat integration.
There are few bugs in two areas actually:
1) Documentation to Heat incorrectly describers procedure of creating custom image
2) Installation of Heat's agents don't work when creating Xenial-based custom image
==== Documentation ===
a) https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#custom-image-script says that the following command
git clone https://git.openstack.org/openstack/diskimage-builder.git
is enough to launch diskimage-builder. That's wrong at the moment - just git'ing diskimage-builder's tree don't provide access to required executables, one need to install it (preferably in virtualenv) in the way like this :
$ virtualenv dib
$ source dib/bin/activate
$ git clone https://git.openstack.org/openstack/diskimage-builder
$ cd diskimage-builder
$ pip install -e .
and just then all next steps are possible:
git clone https://git.openstack.org/openstack/tripleo-image-elements.git
git clone https://git.openstack.org/openstack/heat-agents.git
[ ... ]
b) I guess, it makes sense to note there are different branches of tripleo-image-elements / heat-agents and one need to distinguish between them: master, stable/ocata or stable/newton, e.g.
git clone -b stable/ocata https://git.openstack.org/openstack/tripleo-image-elements.git
git clone -b stable/ocata https://git.openstack.org/openstack/heat-agents.git
c) to proper work of os-*-config tools, it's required to have dib-run-parts tool on host VM, which need to be added to BASE_ELEMENTS variable (last entry in the following row):
export BASE_ELEMENTS="ubuntu selinux-permissive dib-run-parts"
==== Code ====
Few fixes required to diskimage-builder's elements to work with Xenial distribution:
d) in Xenial, dib-run-parts tool resides in 'python-dib-utils' package, which need to be reflected in diskimage-builder/diskimage_builder/elements/dib-run-parts/package-installs.yaml instead of 'dib-utils' (see (c) above)
e) heat-config-notify (used for notifying Heat about changes on VM) require keystoneclient, so this package need to be added to heat-agents/heat-config/install.d/heat-config-source-install/50-heat-config-soure (last entry in the following row):
pip install python-heatclient python-zaqarclient python-keystoneclient
f) there is broken dependency in os-collect-config's systemd integration, which prevents it starting upon VM start/reboot. This can be fixed using the following change in tripleo-image-elements/elements/os-collect-config/install.d/os-collect-config-source-install/10-os-collect-config:
[Install]
WantedBy=cloud-init.target
instead of "WantedBy=multi-user.target"
After all these changes, I was be able to create and launch xenial-based custom image using diskimage-builder tool.
Hope this'll help. Thank you. |
Dears,
Summary: I wasn't be able to create xenial-based custom image with Heat integration.
There are few bugs in two areas actually:
1) Documentation to Heat incorrectly describers procedure of creating custom image
2) Installation of Heat's agents don't work when creating Xenial-based custom image
==== Documentation ===
a) https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#custom-image-script says that the following command
git clone https://git.openstack.org/openstack/diskimage-builder.git
is enough to launch diskimage-builder. That's wrong at the moment - just git'ing diskimage-builder's tree don't provide access to required executables, one need to install it (preferably in virtualenv) in the way like this :
$ virtualenv dib
$ source dib/bin/activate
$ git clone https://git.openstack.org/openstack/diskimage-builder
$ cd diskimage-builder
$ pip install -e .
and just then all next steps are possible:
git clone https://git.openstack.org/openstack/tripleo-image-elements.git
git clone https://git.openstack.org/openstack/heat-agents.git
[ ... ]
b) I guess, it makes sense to note there are different branches of tripleo-image-elements / heat-agents and one need to distinguish between them: master, stable/ocata or stable/newton, e.g.
git clone -b stable/ocata https://git.openstack.org/openstack/tripleo-image-elements.git
git clone -b stable/ocata https://git.openstack.org/openstack/heat-agents.git
c) to proper work of os-*-config tools, it's required to have dib-run-parts tool on host VM, which need to be added to BASE_ELEMENTS variable (last entry in the following row):
export BASE_ELEMENTS="ubuntu selinux-permissive dib-run-parts"
==== Code ====
Few fixes required to diskimage-builder's elements to work with Xenial distribution:
d) in Xenial, dib-run-parts tool resides in 'python-dib-utils' package, which need to be reflected in diskimage-builder/diskimage_builder/elements/dib-run-parts/package-installs.yaml instead of 'dib-utils' (see (c) above)
e) heat-config-notify (used for notifying Heat about changes on VM) require keystoneclient, so this package need to be added to heat-agents/heat-config/install.d/heat-config-source-install/50-heat-config-soure (last entry in the following row):
pip install python-heatclient python-zaqarclient python-keystoneclient
f) there is broken dependency in os-collect-config's systemd integration, which prevents it starting upon VM start/reboot. This can be fixed using the following change in tripleo-image-elements/elements/os-collect-config/install.d/os-collect-config-source-install/10-os-collect-config:
[Install]
WantedBy=cloud-init.target
instead of "WantedBy=multi-user.target"
After all these changes, I was be able to create and launch xenial-based custom image using diskimage-builder tool. Possibly, it can brake Trusty-based installation, this needs to be checked when considering changes above.
Hope this'll help. Thank you. |
|
| 2017-05-19 07:34:06 |
Volodymyr Litovka |
description |
Dears,
Summary: I wasn't be able to create xenial-based custom image with Heat integration.
There are few bugs in two areas actually:
1) Documentation to Heat incorrectly describers procedure of creating custom image
2) Installation of Heat's agents don't work when creating Xenial-based custom image
==== Documentation ===
a) https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#custom-image-script says that the following command
git clone https://git.openstack.org/openstack/diskimage-builder.git
is enough to launch diskimage-builder. That's wrong at the moment - just git'ing diskimage-builder's tree don't provide access to required executables, one need to install it (preferably in virtualenv) in the way like this :
$ virtualenv dib
$ source dib/bin/activate
$ git clone https://git.openstack.org/openstack/diskimage-builder
$ cd diskimage-builder
$ pip install -e .
and just then all next steps are possible:
git clone https://git.openstack.org/openstack/tripleo-image-elements.git
git clone https://git.openstack.org/openstack/heat-agents.git
[ ... ]
b) I guess, it makes sense to note there are different branches of tripleo-image-elements / heat-agents and one need to distinguish between them: master, stable/ocata or stable/newton, e.g.
git clone -b stable/ocata https://git.openstack.org/openstack/tripleo-image-elements.git
git clone -b stable/ocata https://git.openstack.org/openstack/heat-agents.git
c) to proper work of os-*-config tools, it's required to have dib-run-parts tool on host VM, which need to be added to BASE_ELEMENTS variable (last entry in the following row):
export BASE_ELEMENTS="ubuntu selinux-permissive dib-run-parts"
==== Code ====
Few fixes required to diskimage-builder's elements to work with Xenial distribution:
d) in Xenial, dib-run-parts tool resides in 'python-dib-utils' package, which need to be reflected in diskimage-builder/diskimage_builder/elements/dib-run-parts/package-installs.yaml instead of 'dib-utils' (see (c) above)
e) heat-config-notify (used for notifying Heat about changes on VM) require keystoneclient, so this package need to be added to heat-agents/heat-config/install.d/heat-config-source-install/50-heat-config-soure (last entry in the following row):
pip install python-heatclient python-zaqarclient python-keystoneclient
f) there is broken dependency in os-collect-config's systemd integration, which prevents it starting upon VM start/reboot. This can be fixed using the following change in tripleo-image-elements/elements/os-collect-config/install.d/os-collect-config-source-install/10-os-collect-config:
[Install]
WantedBy=cloud-init.target
instead of "WantedBy=multi-user.target"
After all these changes, I was be able to create and launch xenial-based custom image using diskimage-builder tool. Possibly, it can brake Trusty-based installation, this needs to be checked when considering changes above.
Hope this'll help. Thank you. |
Dears,
Summary: I wasn't be able to create xenial-based custom image with Heat integration.
There are few bugs in two areas actually:
1) Documentation to Heat incorrectly describers procedure of creating custom image
2) Installation of Heat's agents don't work when creating Xenial-based custom image
==== Documentation ===
a) https://docs.openstack.org/developer/heat/template_guide/software_deployment.html#custom-image-script says that the following command
git clone https://git.openstack.org/openstack/diskimage-builder.git
is enough to launch diskimage-builder. That's wrong at the moment - just git'ing diskimage-builder's tree don't provide access to required executables, one need to install it (preferably in virtualenv) in the way like this :
$ virtualenv dib
$ source dib/bin/activate
$ git clone https://git.openstack.org/openstack/diskimage-builder
$ cd diskimage-builder
$ pip install -e .
and just then all next steps are possible:
git clone https://git.openstack.org/openstack/tripleo-image-elements.git
git clone https://git.openstack.org/openstack/heat-agents.git
[ ... ]
b) I guess, it makes sense to note there are different branches of tripleo-image-elements / heat-agents and one need to distinguish between them: master, stable/ocata or stable/newton, e.g.
git clone -b stable/ocata https://git.openstack.org/openstack/tripleo-image-elements.git
git clone -b stable/ocata https://git.openstack.org/openstack/heat-agents.git
c) to proper work of os-*-config tools, it's required to have dib-run-parts tool on host VM, which need to be added to BASE_ELEMENTS variable (last entry in the following row):
export BASE_ELEMENTS="ubuntu selinux-permissive dib-run-parts"
==== Code ====
Few fixes required to diskimage-builder's elements to work with Xenial distribution:
d) in Xenial, dib-run-parts tool resides in 'python-dib-utils' package, which need to be reflected in diskimage-builder/diskimage_builder/elements/dib-run-parts/package-installs.yaml instead of 'dib-utils' (see (c) above)
e) heat-config-notify (used for notifying Heat about changes on VM) require keystoneclient, so this package need to be added to heat-agents/heat-config/install.d/heat-config-source-install/50-heat-config-soure (last entry in the following row):
pip install python-heatclient python-zaqarclient python-keystoneclient
f) there is broken dependency in os-collect-config's systemd integration, which prevents it starting upon VM start/reboot. This can be fixed using the following change in tripleo-image-elements/elements/os-collect-config/install.d/os-collect-config-source-install/10-os-collect-config:
[Install]
WantedBy=cloud-init.target
instead of "WantedBy=multi-user.target"
After all these changes, I was be able to create and launch xenial-based custom image using diskimage-builder tool. Possibly, it can break Trusty-based installation, this needs to be checked when considering changes above.
Hope this'll help. Thank you. |
|
| 2017-06-07 12:20:17 |
Rico Lin |
bug task added |
|
tripleo |
|
| 2017-06-07 12:22:43 |
Rico Lin |
heat: status |
New |
Triaged |
|
| 2017-07-05 10:01:02 |
Rico Lin |
heat: importance |
Undecided |
Low |
|
| 2017-09-22 21:06:57 |
Alex Schultz |
affects |
tripleo |
diskimage-builder |
|
| 2018-05-07 07:49:01 |
Rico Lin |
heat: milestone |
|
no-priority-tag-bugs |
|
