Fuel-mirror uses Packetary to download necessary packages. In turn, Packetary gets a list of mandatory packages, parses their metadata and recursively resolves all their dependencies and then downloads all necessary packages. So, it is kind of self validating. If there were no errors while cloning repos, then everything should be ok.
List of necessary packages is here [1]. This yaml file is installed into /usr/share/fuel-mirror/ubuntu.yaml. Of course, user can run fuel-mirror with custom yaml file (with custom list of packages). [1] https://github.com/openstack/fuel-mirror/blob/master/contrib/fuel_mirror/data/ubuntu.yaml#L72-L133 Vladimir Kozhukalov On Tue, May 3, 2016 at 2:37 PM, Drakopoulos, Dionisis (Nokia - GR/Athens) < [email protected]> wrote: > > Hello world! > Using FUEL release 8 and in specific fuel-mirror to create a local Ubuntu > & OpenStack repository. > > Is there a feature which can validate that all mandatory packages have > been downloaded successfully and that a new IaaS can be commissioned > without any issue? > > Or any other solution - suggestion which will accomplish the same goal? > > Thank you in advance! > > Sent from my Windows Phone > ------------------------------ > From: EXT Srinivasreddy R <[email protected]> > Sent: 03/05/2016 12:17 > To: [email protected] > Subject: [Openstack] liberty release architecture understanding > > Hi all, > i have a three node architecture setup with ice-house release .It is > having a separate network node . > In liberty release as per the documentation there is no network node in > architecture diagram , instead it is suggesting to install the notwork > services on controller node . > > 1. what is the reason for this architectural change .? > 2. can i go with separate Network node in liberty release as well . what > are the advantages and disadvantages . > > Am i missing something ? > > http://docs.openstack.org/liberty/install-guide-ubuntu/overview.html > > > > -------- > thanks > srinivas. > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
