[one-users] New contextualization packages

[Javier Fontan]

On Tue, Dec 18, 2012 at 4:47 PM, Gary S. Cuozzo <gary at isgsoftware.net> wrote:
> [...]
> I'm happy to share them if you let me know how best to do so.  They are quick & dirty but you can easily clean them up to make them acceptable to include with ONE.

There are several methods you can contribute patches. One is forking
our repository to a publicly accessible repository (like github). Hack
a bit, make commits in a themed branch and send us a pull request or
just a link to the repository/branch. For small changes this may be
too cumbersome, tho. For these small changes or standalone files you
can just send patches/files to the mailing list or create a new ticket
in http://dev.opennebula.org and attach them there. If you are sending
patches, giving us the commit (or release) the patch was created from
is really useful to us.

>[...]
>> One
>> possible solution is having two set of configuration scripts, one
>> that
>> starts early in the boot process (for network, hostname and such) and
>> another list for late configuration or service startup scripts. What
>> do you think about it?
>
> I think this is a great idea.  Honestly I don't know enough about the details of the upstart stuff, but I think having an easy way to make scripts that hook into various points in the boot process would be quite nice.  Even if it were as simple as having some sub-directories under the one-context.d directory that were related to the stages of boot.  Sort of a context-based rc#.d directories.

I'll take a look into this. It should not be too difficult to do but I
still have some other work in my queue so I may put this into the back
burner. I've created a ticket so we don't forget this:

http://dev.opennebula.org/issues/1703

Cheers

--
Javier Fontán Muiños
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | jfontan at opennebula.org | @OpenNebula