lp://qastaging/~smoser/maas-images/trunk.centos-keys
- Get this branch:
- bzr branch lp://qastaging/~smoser/maas-images/trunk.centos-keys
Branch merges
Branch information
Recent revisions
- 238. By Scott Moser
-
support for storing keyrings and reading of centos cloudimg .asc files
A couple things here
== pubkey data stored in bzr ==
the tools/pubkeys-to-keyring comes from ubuntu- cloudimage- keyring package.
that then allows you to store ascii armorred files
in bzr and generate the keyring to verify against from those.You can then do:
./tools/pubkeys- to-keyring centos.gpg pubkeys/ centos/ *.gpg And use '--keyring=
./cents. gpg' to gpg. pubkeys/
centos/ README. txt, describes where these keys came from
and why we should trust them.== Usage of the code to verify ==
We should probably move the get_file_sums_list( ) from meph2.netinst
to util.py, but the following illustrates its use. It uses gpgv to
verify the data against the keyring created above.from meph2 import netinst
keyring="./centos. gpg"
burl="http://cloud.centos. org/centos/ 7/images/"
centos_suminfo= (("sha256", "sha256sum.txt.asc" , True),)
print(
netinst.get_file_ sums_list(
burl, keyring=keyring, suminfo=centos_ suminfo) ) - 237. By Scott Moser
-
tox: run make 'meph2-util' in minimal python3 environment
The last merge caused meph2-util to fail to run on our build environment.
This adds a very minimal test that would have actually failed there.We just run meph2-util in the tox env. The imports of yaml and of
requests would have caused this to fail previously. - 236. By Scott Moser
-
use /usr/bin/env for shebang
this means that inside tox, running these will not get
outside dependencies resolved. - 235. By Scott Moser
-
build system now has python3-yaml
Thus revert revno 233:
only import yaml in 'import' subcommandthe build system does not currently have python3-yaml
which causes issues. So for the moment, work around that. - 234. By Scott Moser
-
catch 404 when mining data
when replacing the use of requests, the new code was being more
strict. The requests library would return the 404 document on
non-existent, and then we would end up loading apache dirs from
that. That would result in empty list.Instead of that mention the 404.
- 233. By Scott Moser
-
only import yaml in 'import' subcommand
the build system does not currently have python3-yaml
which causes issues. So for the moment, work around that. - 232. By Scott Moser
-
remove 'requests' dependency for meph2-util, 'import' cleanups.
This removes the requests dependency that was added under meph2-util
and adds 'url_helper' for using urls in meph2.Also utilizes a cache and temp dirs in maas-qcow2targz.
cleanups in system-setup to do the right thing and be aware of
our new python3-yaml depends. - 231. By Scott Moser
-
support importing centos images
* The import command reads from a specified yaml file which defines
the source of the images, the content_id of the stream,
a template for the product_id, and the versions to be downloaded* This consumes the CentOS generic cloud images which use the
standard kernel and have cloud-init preinstalled in qcow2 format.
Since they don't provide a simplestream containing these images
but do provide a sha256sum.txt in a static location it uses
that as the source of metadata* CentOS uses a date stamp as their version so we pull that string out as the
version-id. Since CentOS published two versions of CentOS 7.0 we
import two versions.* CentOS 7.0 has deprecated python-oauth in favor of python-oauth2.
This is despite the fact that the version of cloud-init that
they ship with uses python-oauth in
/usr/lib/python2. 7/site- packages/ cloudinit/ sources/ DataSourceMAAS. py.
This forced me to pull a build of python-oauth from EPEL-testing.* The curtin files pulled from
lp:~blake-rouse/maas-image-builder/trunk/files/head:/contrib/centos/ - 230. By Scott Moser
-
kpack-from-image: avoid 'find' errors if no dtb path
Looking at otherwise successful logs, we would see:
find: `/lib/firmware/4.2.0-7- generic/ device- tree': No such file .. This will avoid those evil looking messages.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://qastaging/maas-images