File size: 3,152 Bytes
4aa5fce |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
=== zz_CyberJacob is now known as CyberJacob === CyberJacob is now known as zz_CyberJacob [12:10] <ejat> openstack-dashboard timeout when i tried to login [12:10] <ejat> what should i do ? [13:05] <mup> Bug #1468726 changed: Retain page position on refresh <ui> <MAAS:Won't Fix> <https://launchpad.net/bugs/1468726> [14:21] <kiko> good morning [17:51] <mup> Bug #1497392 opened: maas text-mode "node-group-interface" bug fails with MAAS 1.8.2+bzr4041-0ubuntu1~trusty1 <MAAS:New> <https://launchpad.net/bugs/1497392> [18:00] <mup> Bug #1497392 changed: maas text-mode "node-group-interface" bug fails with MAAS 1.8.2+bzr4041-0ubuntu1~trusty1 <MAAS:New> <https://launchpad.net/bugs/1497392> [18:03] <mup> Bug #1497392 opened: maas text-mode "node-group-interface" bug fails with MAAS 1.8.2+bzr4041-0ubuntu1~trusty1 <MAAS:New> <https://launchpad.net/bugs/1497392> [19:15] <nodtkn> Howdy. The ubuntu vivid root-tgz files are missing the python-yaml package that is required for me to juju add a newly installed node. Does anyone know of documentation for modifying the root image. Ideally I would like to mount it, add the python-yaml package, unmount it, and load it as a custom image in MAAS. [19:20] <mgz> nodtkn: can't you just add python-yaml in your cloud-config in your dependencies? using non-stock root images is generally a bad idea. [19:21] <mgz> also, juju doesn't depend on python-yaml. [19:28] <nodtkn> mgz: I have modified my preseed files to install python-yaml, but that adds to my installation time. I am always installing a few things like build-essentials so I would rather do it in a custom image. [19:30] <nodtkn> mgz: Are you sure about python-yaml not being required. I was getting errors when I attempted to add vivid nodes and preinstalling python-yaml removed those erros. [19:30] <nodtkn> mgz: It might have been that bootstrap was failing instead of add-machine. === jfarschman is now known as MilesDenver [19:43] <ennoble> Is there a way to have maas install on a specific type of media (e.g. hd vs. ssd vs. nvme)? [19:46] <nodtkn> mgz: My mistake it was a failure at juju deploy so I would have to log in to the host and run apt-get install python-yaml before I could deploy a service that used charmhelpers. [19:49] <mgz> nodtkn: yeah, you just want to fix the charm install hook it sounds like [19:55] <nodtkn> mgz: That would be nice, but I generally I think the ability to create a custom ubuntu image would be awesome. I could modify it to run the latest kernel, update all of the packages (instead having to call apt-get upgrade), and install all of the common packages that are needed by my charms. [20:10] <roaksoax> /w/win 7 [21:26] <kiko> nodtkn, yep, we agree -- this is something we've been thinking about how to automate and make easier [21:30] <nodtkn> kiko: I tried out the maas-image-builder I was thinking if it worked for centos I would attempt to modify it to work with ubuntu. === zz_CyberJacob is now known as CyberJacob [22:04] <ennoble> is there a way to control what media maas provisions the machines with when multiple storage types are connected? === ptoohill is now known as pc-pothole |