So actually it is set as I can see with onetemplate show the following:

CONTEXT=[
  NETWORK="YES",
  SSH_PUBLIC_KEY="$USER[SSH_PUBLIC_KEY]" ]

it just doesn't show up in the sunstone interface for some reason. But still 
having this NETWORK=YES custom variable doesn't help my Fedora 20 VM which I 
recreated but still no network...




On Wednesday, June 11, 2014 3:19 PM, Javier Fontan <jfon...@opennebula.org> 
wrote:
That's because that context variable has a checkbox to activate it in
Context -> Network & SSH -> Add Network contextualization. You'll see
that the checkbox is activated.

To make sure it is set you can execute:

onevm show <template>






On Wed, Jun 11, 2014 at 2:35 PM, ML mail <mlnos...@yahoo.com> wrote:
> I tried with NETWORK=YES and Sunstone actually says "Template updated 
> correctly" but still this custom variable is not present or saved in that 
> template, this is really weird.
>
>
>
> On Wednesday, June 11, 2014 2:31 PM, Stefan Kooman <ste...@bit.nl> wrote:
> Quoting ML mail (mlnos...@yahoo.com):
>
>
>
>> I see, then it would be great indeed if this could be adapted for the
>> new ifconfig output or as suggested by someone else on the list use
>> the new ip tool.
>>
>> Strangely enough I tried to add the NETWORK=yes to the custom vars of
>> the template context but even if I click "add" and "update" the next
>> time I view this template the custom variable is gone... Any idea why
>> this custom var is not being saved? I am using ONE 4.6.0.
>
> NETWORK=yes should be all caps if I'm not mistaken, i.e. NETWORK=YES.
> Could you try again?
>
> Gr. Stefan
>
> --
> | BIT BV  http://www.bit.nl/        Kamer van Koophandel 09090351
> | GPG: 0xD14839C6                   +31 318 648 688 / i...@bit.nl
>



-- 
Javier Fontán Muiños
Developer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | @OpenNebula | github.com/jfontan 
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Reply via email to