WebUI
by Leonid Flaks
I see a lot of work is done lately to make WebUI better and wanted to
mention one little and hopefully simple improvement that I think would
be useful. When I look at any specific system I can change parameters
associated with it easily, but the only way to see the rendered
kickstart for it is to go back to the list of systems and click on
kickstart link there. It would be nice to have this link available on
the system page also. If I make a change to a particular meta data, for
example, and want to see how would that effect the resulting ks file.
Thanks,
Leon
13 years, 1 month
Re: Puppet environment field for cobbler
by Scott Henson
On Tue, 5 Apr 2011 13:39:38 -0700, Walker Traylor <walker(a)mog.com> wrote:
> Scott,
>
> Thank you for your reply.
>
> It would be very similar to the way classes are implemented in cobbler, using the --mgmt-classes flag. The only difference is that the environment data is not a list, it is just one field. Also in contrast, the parameters passed to puppet (via --ksmeta) returns a key value array in YAML format. So, environment is another format, and the simplest.
>
>
> Check out this for sample YAML that puppet expects for classes, environment, and parameters: http://docs.puppetlabs.com/guides/external_nodes.html
>
> Look in the box under "External node scripts for version 0.23 and later"
>
> A --mgmt-environment flag would be my preferred method, for consistency, ie:
>
> #cobbler system add mysystem.mog.com --mgmt-environment="dev" --mgmt-classes="base webserver devusers"
>
>
> The functionality that this provides, is puppet can be configured to serve up puppet manifests from different directory trees depending on "environment." This is a big deal to us because we are using puppet to manage production systems, yet also doing lots of class development for more variable boxes. One wrong move on the production scripts could kill everything (wrong nslookup, user, etc.) but I need to be able to hack on those with plenty of leeway for trial and error in our development deployment environment. The work around is run multiple puppet instances on different ports, but that is messy and now we have this nice feature in puppet built in to support this - may as well use it.
>
> Let me know if you have any other questions, or how else I may support this.
In our setup we implemented environments as part of the hostname
(e.g. foo.app.dev.example.com). Then we put an override in the
parameters section. Basically have a key called environment in the
ksmeta that would be able to override the default set by dns. I don't
have a problem with what you are asking for, I'm just not sure if it is
needed given that you can put it in ksmeta. Do you see some reason?
--
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
13 years, 1 month
[PATCH] Minor change to validate a token before checking on a user
by James Cammarata
Pushed to my github:
https://github.com/jimi1283/cobbler/commit/fe814e8923ba952f91d53b83144199...
commit fe814e8923ba952f91d53b831441995a2ddfff83
Author: James Cammarata <jimi(a)sngx.net>
Date: Sun Apr 3 09:19:27 2011 -0500
Minor change to validate a token before checking on a user.
When cobblerd expires a token after the timeout (1 hour), weird
things can happen because the get_user_from_token() function only
checks to see if the token is in the cache - not that it's valid.
This should be cherry-picked - don't pull the whole master branch.
There is another commit before it
(382b20cd08321810e03a7690e13bb39b5f5c61b9) which is my current work on
the webui that is not ready to be merged (I committed that first
before running across the bug I fix in the above patch).
This patch makes a few minor changes to the remote.py file, so that a
token can be validated before trying to use it.
13 years, 1 month
[PATCH] fixes for webui issues
by James Cammarata
Pushed to my github:
https://github.com/jimi1283/cobbler/commit/41a92b11969ab9c30b749ab99be705...
https://github.com/jimi1283/cobbler/commit/794841821653f8d46257ca743adf17...
commit 794841821653f8d46257ca743adf175977ef3bd3
Author: James Cammarata <jimi(a)sngx.net>
Date: Wed Mar 30 16:43:26 2011 -0500
Fix for django traceback when logging into the web interface with
a bad username and/or password
commit 41a92b11969ab9c30b749ab99be70566cd943093
Author: James Cammarata <jimi(a)sngx.net>
Date: Wed Mar 30 16:42:18 2011 -0500
Fix for snippet/kickstart editing via the web interface, where a
'tainted file path' error was thrown
The solution I came up with for the snippet/kickstart editing issue
was to insert the string 'file:' in front of the file name. This
seems to work well, though I could find no reason why this suddenly
broke (and I'm kind of wondering why it worked in the first place...).
13 years, 1 month
[PATCH] Yet another change to multiselect editing
by James Cammarata
Pushed to my github:
https://github.com/jimi1283/cobbler/commit/e038de105e4bc0752df55a370459a0...
commit e038de105e4bc0752df55a370459a0b8aa65fa6d
Author: James Cammarata <jimi(a)sngx.net>
Date: Thu Mar 31 23:07:20 2011 -0500
Yet another change to multiselect editing.
Multiselects are now presented as side-by-side add/delete boxes,
where values can be moved back and forth and only appear in one of the
two boxes.
This is all based on the jquery stuff illsci posted in IRC this
evening (http://blog.jeremymartin.name/2008/02/easy-multi-select-transfer-with-jqu...).
It was ridiculously easy and I feel this is the best method for
multi-selects overall.
There's still some cleanup to do, like remove all of the <<None>>
stuff, and we need to figure out some method of using <<inherit>> with
this too. Really, I think <<inherit>> should be an option to add, and
the final result should be the union of the parent profile/distros
data with whatever is selected in the current object, but that will
require some changes to blender/utils I think.
Enjoy!
13 years, 1 month