| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
LP: #1078097
|
|
Fix how the comparison of a fqdn and its aliases was done
via sorting instead of existence checking which is the better
way to check if a alias already exists as well as cleanup
the new files pep8/pylint issues.
LP: #1078097
|
|
Add in entry for LP: 1068801 and LP: 1075756
as well as LP: 1077245 and add in reason why
we are switching back to using 'None' as the
initial datasource value.
|
|
Add in entry for LP: 1068801 and LP: 1075756
as well as LP: 1077245 and add in reason why
we are switching back to using 'None' as the
initial datasource value.
|
|
Previous commit set up an object for checking "None" in the stages class.
Here, change that to be None. The benefit of the DataSourceNone was so that
the stages was generally functional even with that "None" object.
The negative affect of that is that you could go down the error path much
longer when using it. If we use None type, then self.datasource.<something>
will fail immediately and loudly.
|
|
|
|
This just replaces the portions of stages.py that were checking or
setting self.datasource to a DataSourceNone to use a static/global
datasource. And then, check for None is done against that.
|
|
|
|
This does a couple things:
* separates out the 'normalize_public_keys' from the DataSource's get_public_ssh_keys
* uses that from config-drive datasource
* supports config drive v1 or v2 public-keys
* adds a test.
LP: #1077700
|
|
|
|
'public_keys'
|
|
newer versions of boto lazily load the metadata from the ec2
metadata service. Here, we:
1. Add a ec2_utils module that checks which version of boto is being used and
under the right versions the metadata dictionary will be expanded.
2. Use this new ec2_utils module in the cloudstack and ec2
datasources as there entrypoints into boto.
3. Add a dependency on python-pkg-resources (from pkg_resources import
parse_version) to determine the boto version.
LP: #1068801
|
|
|
|
|
|
|
|
other datasources populate 'public-keys' rather than 'public_keys'
and there is a more complete handler in the base DataSource.
So, to take advantage of that, have DataSourceConfigDrive copy
public_keys to public-keys, and remove the 'get_public_ssh_keys'
from the DataSourcEConfigDrive.
LP: #1077700
|
|
These changes were pulled out of the previous merge (cc_yum_add_repo)
as they were unrelated there. Re-applying them here.
|
|
Add in a configuration module that can write out the yum.repo format for
those that want to hook into different repos for installing.
|
|
|
|
|
|
|
|
This migrator module does a few things
* fixes filename markers that were written with a '-' in them to have
an '_' instead
* support renaming modules. Explicitly this handles the name change
of 'apt-update-upgrade' to 'apt-configure' and
'package-update-upgrade-install'
Also, just be more consistent everywhere where writing semaphore/marker
files and use '_' instead of '-' (canon_sem_name).
|
|
LP: #1076811
|
|
|
|
|
|
when that group configuration is a dict => members.
LP: #1077245
|
|
|
|
|
|
where rhel uses the fqdn for its config while
ubuntu uses the short hostname.
|
|
|
|
|
|
the fully qualified domain name should end
up in /etc/sysconfig/network by passing the
fqdn to the update and set hostname methods
and using it accordingly.
LP: #1076759
|
|
reflected when running in the init stage
after user-data has been loaded.
|
|
of the init class are reset so that when they are
regenerated that they will use the updated data
instead of using previous data (since they weren't reset).
LP: #1076811
|
|
bad yamls are found instead
of returning zero in that case.
|
|
This change does 3 things:
* revert the fix from revno 697
* minor clean up some local variable usage and definition
* make Z99-cloud-locale-test.sh actually work when shell is zsh
the last is done by detecting if this is zsh, and if so, changing the zsh
behavior for this function to emulate sh. As a result of the '-L' in
'emulate -L sh', we have no negative affect on the user's shell.
LP: #1073077
|
|
This makes zsh act like 'sh', but only for the function local function.
This way, we do not affect the user's shell, but get the behavior we
want.
|
|
|
|
|
|
is actually a valid value returned.
2. Adjust variable naming
|
|
when applying the canon routine.
2. Add in a function to migrate legacy
semaphores to new semaphores.
|
|
that can be used to aid in the moving
of older versions of cloud-inits data
to newer versions of cloud-inits data.
1. Move the semaphores for the current instance
to there canonicalized names and use the
canonicalized in the file 'locking' code
|
|
and fix the cases where the cc yaml
is not correct.
|
|
2. Added example cloud-config
3. Added functioning test for yum config
|
|
|
