[one-users] Problem while creating VMs

[Carlos Martín Sánchez]

Hi,

On Tue, Jun 10, 2014 at 1:35 PM, Duverne, Cyrille <
cyrille.duverne at euranova.eu> wrote:

> Thanks a lot Martin and Stuart, that's much appreciated !
>
> Concerning the second part about the template update, any thought ?
>
> Regards
> Cyrille
>

You template should be working in 4.6, I think. If you prefer to use the
context packages we provide, then the new easier way to set the network
contextualization is described here [1]:

In the VM template contextualization we set NETWORK to yes:
> CONTEXT=[
>   NETWORK=YES ]



When the template is instantiated, those parameters for eth0 are
> automatically set in the VM as:
> CONTEXT=[
>   DISK_ID="0",
>   ETH0_DNS="8.8.8.8 8.8.4.4",
>   ETH0_GATEWAY="80.0.0.1",
>   ETH0_IP="80.0.0.2",
>   ETH0_MASK="255.255.255.0",
>   ETH0_NETWORK="80.0.0.0",
>   NETWORK="YES",
>   TARGET="hda" ]


> If you add more that one interface to a Virtual Machine you will end with
> same parameters changing ETH0 to ETH1, ETH2, etc.


> You can also add SSH_PUBLIC_KEY parameter to the context to add a SSH
> public key to the authorized_keys file of root.


[1]
http://docs.opennebula.org/4.6/user/virtual_machine_setup/bcont.html#preparing-the-template

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org <http://www.opennebula.org/> | cmartin at opennebula.org |
@OpenNebula <http://twitter.com/opennebula> <cmartin at opennebula.org>



>
> At Tuesday, 10/06/2014 on 11:45 Carlos Martín Sánchez wrote:
>
> Hi,
>
> On Sun, Jun 8, 2014 at 2:47 PM, Stuart Longland <stuartl at vrt.com.au>
> wrote:
>
>> On 08/06/14 19:29, Duverne, Cyrille wrote:
>> > Hello Guys !
>> >
>> > I've upgraded to 4.6 and I'm now able to create VMs.
>> > Some questions still :
>> >
>> > - When, from sunstone, I want to create a new VM following a template
>> > (4.2 compliant), they are stuck in PENDING state until I click on
>> > "Deploy" -> I've browse the doc without finding precise explanation on
>> > this behaviour of the scheduler.
>>
>> I've noticed this from time to time too.  Sometimes it's just a matter
>> of waiting a few minutes for the scheduler to pick up on them, but
>> manually deploying seems to give the whole system the kicking it needs.
>>
>
> The scheduling timer can be changed in the sched.conf file [1].
>
> If the scheduler can't find where to deploy a VM, the reason can be found
> in the SCHED_MESSAGE variable (visible in the placement section of the VM
> view in sunstone).
> For more detailed reasons or error messages, you can check the
> /var/log/one/sched.log file.
>
> Regards
>
> [1] http://docs.opennebula.org/4.6/administration/references/schg.html
>
> --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org <http://www.opennebula.org/> | cmartin at opennebula.org
>  | @OpenNebula <http://twitter.com/opennebula> <cmartin at opennebula.org>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140611/cf598073/attachment-0001.htm>