Ask Your Question

Revision history [back]

Due to need set MTU 1454 for some time I used creating instances in cluster via command

[root@dfw02 ~(keystone_boris)]$  nova boot --flavor 2 --user-data=./myfile.txt  
    --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
where

[root@dfw02 ~(keystone_boris)]$  cat ./myfile.txt
#cloud-config
 password: mysecret
 chpasswd: { expire: False }
 ssh_pwauth: True

 Same is possible via Post Creation Tab's Customization Script Window
 in Dashboard. Instance been created won't require keypair at all.

Just  
# ssh ubuntu@compute-node will login you with password "mysecret"

I am not sure that is what you are asking about.
In meantime I set MTU via dhcp_agent.ini&dnsmasq.conf  and don't do it anymore

Due to need set MTU 1454 for some time I used creating instances in cluster via command

 [root@dfw02 ~(keystone_boris)]$  nova boot --flavor 2 --user-data=./myfile.txt  
     --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
 where

 [root@dfw02 ~(keystone_boris)]$  cat ./myfile.txt
 #cloud-config
  password: mysecret
  chpasswd: { expire: False }
  ssh_pwauth: True

  Same is possible via Post Creation Tab's Customization Script Window
  in Dashboard. Instance been created won't require keypair at all.

 Just  
 # ssh ubuntu@compute-node will login you with password "mysecret"

 I am not sure that is what you are asking about.
 In meantime I set MTU via dhcp_agent.ini&dnsmasq.conf  and don't do it anymore

Due to need set MTU 1454 for some time I used creating instances in cluster via command

  [root@dfw02 ~(keystone_boris)]$  nova boot --flavor 2 --user-data=./myfile.txt  
         --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
     where

     [root@dfw02 ~(keystone_boris)]$  cat ./myfile.txt
     #cloud-config
     password: mysecret
     chpasswd: { expire: False }
     ssh_pwauth: True

      Same is possible via Post Creation Tab's Customization Script Window
      in Dashboard. Instance been created won't require keypair at all.

     Just  
     # ssh ubuntu@compute-node will login you with password "mysecret"

     I am not sure that is what you are asking about.
     In meantime I set MTU via dhcp_agent.ini&dnsmasq.conf  and don't do it anymore
I just cannot remind works or not command like :-

$ nova keypair-add oskey1 > oskey1.priv
$  nova boot --flavor 2 --key_name oskey1 --user-data=./myfile.txt  
            --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
but it's not a problem to test

Due to need set MTU 1454 for some time I used creating instances in cluster via command

  [root@dfw02 ~(keystone_boris)]$  nova boot --flavor 2 --user-data=./myfile.txt  
             --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
         where

         [root@dfw02 ~(keystone_boris)]$  cat ./myfile.txt
         #cloud-config
         password: mysecret
         chpasswd: { expire: False }
         ssh_pwauth: True

          Same is possible via Post Creation Tab's Customization Script Window
          in Dashboard. Instance been created won't require keypair at all.

         Just  
         # ssh ubuntu@compute-node will login you with password "mysecret"

         I am not sure that is what you are asking about.
         In meantime I set MTU via dhcp_agent.ini&dnsmasq.conf  and don't do it anymore
I just cannot remind works or not command like :-

$ nova keypair-add oskey1 > oskey1.priv
$  nova boot --flavor 2 --key_name oskey1 --user-data=./myfile.txt  
            --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
but it's not a problem to test

Due to need set MTU 1454 for some time I used creating instances in cluster via command

            [root@dfw02 ~(keystone_boris)]$  nova boot --flavor 2 --user-data=./myfile.txt  
                --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
            where

            [root@dfw02 ~(keystone_boris)]$  cat ./myfile.txt
            #cloud-config
            password: mysecret
            chpasswd: { expire: False }
            ssh_pwauth: True

             Same is possible via Post Creation Tab's Customization Script Window
             in Dashboard. Instance been created won't require keypair at all.

            Just  
            # ssh ubuntu@compute-node will login you with password "mysecret"

            I am not sure that is what you are asking about.
            In meantime I set MTU via dhcp_agent.ini&dnsmasq.conf  and don't do it anymore

Tested just now $ ssh fedora@192.168.1.119 The authenticity of host '192.168.1.119 (192.168.1.119)' can't be established. ECDSA key fingerprint is e7:ee:95:08:28:8d:32:58:fc:79:28:e5:d0:c7:6f:34. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.1.119' (ECDSA) to the list of known hosts. fedora@192.168.1.119's password: Last login: Sun Apr 6 13:55:00 2014 from 192.168.1.130 [fedora@vf20rs0408 ~]$ uname -a Linux vf20rs0408 3.13.8-200.fc20.x86_64 #1 SMP Tue Apr 1 03:35:46 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Due to need set MTU 1454 for some time I used creating instances in cluster via command

            [root@dfw02 ~(keystone_boris)]$  nova boot --flavor 2 --user-data=./myfile.txt  
                --image 03c9ad20-b0a3-4b71-aa08-2728ecb66210 UbuntuTRS01
            where

            [root@dfw02 ~(keystone_boris)]$  cat ./myfile.txt
            #cloud-config
            password: mysecret
            chpasswd: { expire: False }
            ssh_pwauth: True

             Same is possible via Post Creation Tab's Customization Script Window
             in Dashboard. Instance been created won't require keypair at all.

            Just  
            # ssh ubuntu@compute-node will login you with password "mysecret"

            I am not sure that is what you are asking about.
            In meantime I set MTU via dhcp_agent.ini&dnsmasq.conf  and don't do it anymore

Tested just now $ ssh fedora@192.168.1.119 fedora@192.168.1.119

The authenticity of host '192.168.1.119 (192.168.1.119)' can't be established.
ECDSA key fingerprint is e7:ee:95:08:28:8d:32:58:fc:79:28:e5:d0:c7:6f:34.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.119' (ECDSA) to the list of known hosts.
fedora@192.168.1.119's password: 
Last login: Sun Apr  6 13:55:00 2014 from 192.168.1.130
[fedora@vf20rs0408 ~]$ uname -a
Linux vf20rs0408 3.13.8-200.fc20.x86_64 #1 SMP Tue Apr 1 03:35:46 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

GNU/Linux