~maas-maintainers/maas/auto-merge-test : changes

~maas-maintainers/maas/auto-merge-test » Changes from revision 1000

From Revision 1000 to 981

Rev	Summary	Authors	Date
1000	[r=matsubara][bug=][author=matsubara] foo bar precise [r=matsubara][bug=][author=matsubara] foo bar precise	Diogo Matsubara	11 years ago
999	[r=matsubara][bug=][author=matsubara] test test [r=matsubara][bug=][author=matsubara] test test	Diogo Matsubara	11 years ago
998	[r=matsubara][bug=][author=matsubara] test [r=matsubara][bug=][author=matsubara] test	Diogo Matsubara	11 years ago
997	[r=matsubara][bug=][author=matsubara] another change [r=matsubara][bug=][author=matsubara] another change	Diogo Matsubara	11 years ago
996	empty checkin empty checkin	MAAS Lander	11 years ago
995	[r=matsubara][bug=][author=matsubara] just a test change [r=matsubara][bug=][author=matsubara] just a test change	Diogo Matsubara	11 years ago
994	make offline=true <target> now keeps buildout and virtualenv... make offline=true <target> now keeps buildout and virtualenv off the network for all targets. Previously there was a build-offline target that permitted an offline build only. This is a more general solution. This is a backport of the changes in lp:~allenap/maas/offline-more.	Gavin Panella	11 years ago
993	Removes the management of production dependencies from the p... Removes the management of production dependencies from the purview of buildout. Dependencies that form the final product will no longer be version controlled by buildout. They are assumed to be available on the system already. This is taken care of by `make install-dependencies`. The only dependencies managed by buildout are for testing and development. This is a backport of lp:~allenap/maas/prod-deps-not-in-buildout and lp:~allenap/maas/lxml-not-a-test-dep from trunk.	Gavin Panella	11 years ago
992	Backport of trunk r1003: Fix incorrect module path on Backport of trunk r1003: Fix incorrect module path on report_boot_images task in beat schedule.	Jeroen Vermeulen	11 years ago
991	Backport trunk r1001. Show persistent error message about m... Backport trunk r1001. Show persistent error message about missing boot images. As per pre-imp with Julian: rather than validate boot requests against available images (for specific architectures, releases etc.) this simpler solution merely checks whether any boot images have been reported at all. The bug this addresses is really just about warning when the import script has not run at all.	Jeroen Vermeulen	11 years ago
990	Backport trunk r999. Have the master worker report its avai... Backport trunk r999. Have the master worker report its available boot images. This creates a new task for the master worker, and runs it on a 5-minute schedule. The task scans the TFTP filesystem tree (which is on the same system as the master worker) for boot images, and reports what it finds to the API. In a subsequent branch, the UI will report missing images as a persistent error.	Jeroen Vermeulen	11 years ago
989	Backport of trunk r996. New API call for the master worker:... Backport of trunk r996. New API call for the master worker: register_boot_images. This is how the master worker will report to the MAAS server which images it has available for net-booting nodes. The API code stores the results in BootImage (see predecessor branch) so that the various operations for booting nodes can check that the required images are really available. If not, it can report the problem to the user and make recommendations for running or reconfiguring the maas-import-pxe-files script. The new call lives on a new API path, boot-images/. I found it didn't quite fit in anywhere. It might have fit at the root, but we're not making a habit of that. Plus, we may want to add querying abilities to the boot images later, for which this separate path is just right. Images are passed in as a JSON-encoded list of dicts. I nearly used a list of tuples, but that would have been error-prone and harder to keep compatible between API versions. The calls aren't very data-intensive so there's little reason to keep the encoding minimal.	Jeroen Vermeulen	11 years ago
988	Fix migration 22: add missing nodegroup.uuid. Remove migrati... Fix migration 22: add missing nodegroup.uuid. Remove migration 25 and re-add it as migration 23.	Raphael Badin	11 years ago
987	Backport from trunk r990. New model: BootImage. Represents a... Backport from trunk r990. New model: BootImage. Represents an available boot image, so that the server can detect use of missing images. This new model represents what types of node we can boot which releases on, for which purpose. Since the inventory only changes when we have a new image, complete and ready to install, there is no provision for disappearing images.	Jeroen Vermeulen	11 years ago
986	[r=jtv][bug=][author=allenap] Add targets to start only the ... [r=jtv][bug=][author=allenap] Add targets to start only the services for a cluster or a region, e.g. run-region and stop-cluster. Previously, only applying an action to an individual service (`make services/<service>/@<action>`, e.g. make services/web/@run) or applying an action to all services at once (`make <action>`, e.g. make run) was possible. Now targets like "start-region" and "status-region" also exist, to apply an action to a subset of all services at once.	Gavin Panella	11 years ago
985	[r=julian-edwards][bug=][author=smoser] if enlistment fails,... [r=julian-edwards][bug=][author=smoser] if enlistment fails, offer login for debug This sets a username password of 'ubuntu:ubuntu' if the user enlistment process fails, and prints a message to the screen about the ability to login with those credentials. Upon login, a file is touched in /tmp , and if that file is present after the script sleeps for 60 seconds, then the reboot is aborted. In the default images, ssh via password auth is disabled, so unless that is enabled, there is no concern of remotely coming in as that user.	Scott Moser	11 years ago
984	[r=julian-edwards][bug=][author=evilnick] This adds a short [r=julian-edwards][bug=][author=evilnick] This adds a short troubleshooting section to the docs	Nick Veitch	11 years ago
983	[r=jtv][bug=][author=rvb] Use the nodegroup UUID to identify... [r=jtv][bug=][author=rvb] Use the nodegroup UUID to identify the nodegroup.	Raphael Badin	11 years ago
982	[r=jtv][bug=][author=rvb] Add a new UUID field to the nodegr... [r=jtv][bug=][author=rvb] Add a new UUID field to the nodegroup. That UUID will be used to uniquely identify a nodegroup.	Raphael Badin	11 years ago
981	[r=jtv][bug=][author=rvb] Add a field to track the status of [r=jtv][bug=][author=rvb] Add a field to track the status of nodegroups.	Raphael Badin	11 years ago

Older »