<head></head><body>As you may now we should integrate solar with
fuel in 9.0. Integration in 9.0 will be very experimental and it will
not affect fuel except: spec <a href="https://review.openstack.org/283600" rel="noreferrer" target="_blank"></a><a href="https://review.openstack.org/283600" rel="noreferrer" target="_blank"><spelling class="misspelled">https</spelling>://review.<spelling class="misspelled">openstack</spelling>.<spelling class="misspelled">org</spelling>/283600</a> and <a href="https://review.openstack.org/#/c/284293/"><spelling class="misspelled">https</spelling>://review.<spelling class="misspelled">openstack</spelling>.<spelling class="misspelled">org</spelling>/#/c/284293/</a><div><div><br></div>We
will introduce 2 new packages solar and <spelling class="misspelled">fuel2solar</spelling> ( + some dependencies) in <spelling class="misspelled">Centos7</spelling>, they will be available in mos-master repository. We would like to include not installed solar and <spelling class="misspelled">fuel2solar</spelling> in 9.0 ISO.</div><div><div><br></div>Predicted <spelling class="misspelled">UX</spelling>:<br>- user will need to install 2 rpm packages: solar and <spelling class="misspelled">fuel2solar</spelling><br>- user will configure everything in fuel-web and then switch to solar <spelling class="misspelled">CLI</spelling> before clicking "deploy" button<div><br></div><div>Our current plan is:<br>1.
create blueprint about introducing these 2 additional packages (and
requirements)<br>2. then should we describe everything again in <spelling class="misspelled">openstack-dev</spelling> ML<br>3. describe this everything in fuel docs<div><br></div><div>Maybe instead blueprint in 1st step should we create full blown fuel-spec ? That spec obviously will not require any QA activities.</div></div></div><div><br></div><div><br></div><div>--</div><div>Warm regards,</div><div>Ję<spelling class="misspelled">drzej</spelling> Nowak</div><div><br></div><div><br></div></body>