aboutsummaryrefslogtreecommitdiffstats
path: root/firstboot
AgeCommit message (Collapse)AuthorFilesLines
2016-11-17No longer hard coding to a specifc network interface name.Harald Jensas1-2/+2
Instead of using a specific network interface name, thi fix fetch all ethernet mac addresses. Then uses this list of mac addresses to do a check if any entries in the list match any of the values in NetConfigDataLookup for a node. If there is a match, the /etc/os-net-config/mapping.yaml file for the node will be written. This fix removes the hard coded interface name 'eth0' used to get a mac address as identifyer for the specific node before. Using a hard coded interface name such as 'eth0' would have failed on most hardware because of "consistent network device names". Fix Bug: #1642551 Change-Id: I6c1d1b4d70b916bc5d9049469df8221f8ab2eb95
2016-11-07Add an optional extra node admin ssh key parameterSteven Hardy1-1/+7
This can be used to pass the e.g. the tripleo-validations ssh key into the deployment. Change-Id: I861b9e2252a9c8122dcf7df261386f1ea5200c4f Related-Bug: #1635226
2016-07-01Add example of creating per-node os-net-config mappingsSteven Hardy1-0/+65
Adds an example of proving a mapping file for all nodes, then extracting the data for each node based on a lookup of the mac address. Some assumptions are made (e.g the hard-coded reference to eth0), but it should be easily modified to suit specific environments. Usage via an enviroment file will look like: resource_registry: OS::TripleO::NodeUserData: os-net-config-mappings.yaml parameter_defaults: NetConfigDataLookup: host1: nic1: "00:c8:7c:e6:f0:2e" host2: nic1: "00:18:7d:99:0c:b6" Note this version requires liberty heat in the undercloud due to the use of a new str_replace feature to serialize the json parameter. Change-Id: I7da9c9d8805e676a383e888a7d77f05d3432ab12
2015-11-24Update typosSwapnil Kulkarni (coolsvap)1-1/+1
Change-Id: Id63c1bcfc34058eb7285698ba9bf86d1cf2025a6
2015-09-03Add NodeAdminUserData interface for "heat-admin" userSteven Hardy1-0/+29
Reinstates the heat-admin user via template user-data, which replaces the previous boothook injected user provided by the (deprecated now removed) heat instance_user option. This has some advantages over the heat.conf option, e.g it allows for much easier customzation of the user configuration (additional SSH keys, adding groups etc), and also in future if we support deploying more than one overcloud you could specify a different user per deployment. Co-Authored-By: Dan Prince <dprince@redhat.com> Change-Id: I2235b9690c01542d8a28ec1c1a4607de751aea29 Closes-Bug: #1229849
2015-05-04Firstboot rsync for development purposesJiri Stransky1-0/+49
Could be used to e.g. make changes to the puppet modules on the fly without the need to rebuild images. Documented in the template description. Change-Id: I6a1fef20d4f4afa4bedac5ea520949697793f0ed
2015-04-24Enable passing optional first-boot user-dataSteven Hardy2-0/+80
Currently all the OS::Nova::Server resource created don't pass any user-data. It's possible to pass user-data as well as using heat SoftwareConfig/SoftwareDeployment resources, and this can be useful when you have simple "first boot" tasks which are possible either via cloud-init, or via simple run-once scripts. This enables passing such data by implementing a new provider resource OS::TripleO::NodeUserData, which defaults to passing an empty mime archive (thus it's a no-op). An example of non no-op usage is also provided. Change-Id: Id0caba69768630e3a10439ba1fc2547a609c0cfe