Hardcoded repos for provisioning node

[Sergey Rudyka]

We have hardcoded repos for provisioning node but inside of environments without Internet access we need possibility to change repos on ISO building stage.

Github link https://github.com/openstack/fuel-web/blob/master/nailgun/nailgun/fixtures/openstack.yaml#L1961

[Aleksey Zvyagintsev (azvyagintsev)]

Moving bug to invalid, due:
1) This repo-list are default, and can be changed via Fuel UI or via fuel cli tool(fuel download env attributes )
2) In case env\fuel don't have direct access to repositories - before starting env deployment, you can create local mirror for all needed repository's with fuel-mirror tool.

[Sergey Rudyka (srudyka)]

Thank you for your answer.
But the ways that you proposed don't fit our requirements.
Our requirement is building ISO and use it for install hundred's environments and editing settings_NN.yaml after "fuel --env NN settings --download" does not fit for us.

[Aleksey Zvyagintsev (azvyagintsev)]

But hardcoding of "some variables" also not good solution.
You can try to use API to automate this process. Like an example: [0]
(In the worth case you can simple create path-set with needed changes and push it to iso-build process)

(buy the way, how you are going to automate env creation\master node installing\node-network configuration end etc.)

[0] https://github.com/openstack/fuel-qa/tree/master/fuelweb_test/models

[Sergey Rudyka (srudyka)]

We are not asking to "hardcode some variables" and run some scripts on fuel master does not fit us because we deploy a lot of environments.

We are requesting about abbility to change default settings in openstack.yaml on ISO building stage.

[Sergey Rudyka (srudyka)]

For instance, it could be default.yaml where default data would be placed

[Andrey Maximov (maximov)]

@Sergey, what if you will have downstream repository of fuel where you can apply various customizations including tweaking ubuntu paths?