ader1990's profile - activity

When you spawn an instance, to set a specific password, you need to use: "nova boot <other options=""> --meta admin_pass=myStrongPassw0rd". If you are already using this, can you provide the cloudbase-init logs on a pastebin, for further debugging?

Hello,

Firstly, if you used the cloudbase-init installer with the sysprep part, the password for the Administrator password is being reset. If you have set Administrator as the default username, its password will be randomly generated by cloudbase-init or taken from the metadata service.

Secondly, there is a delay between the boot process finish and the actual plugin execution, which leads to the behavior you are getting, as the cloudbase-init process takes some time to retrieve the metadata providers. In a cloud scenario, the user does not have access to the vm's console, thus will be unable to connect to that vm until cloudbase-init finishes the createuser and setuserpassword plugins. For example, if you are using OpenStack with http metadata service, the user can retrieve the password using "nova get-password" and use the default username to connect to that Windows vm.

Thanks.

Hello,

If you are using KVM hypervisor, you need to install on the Windows image the VirtIO drivers. The drivers can be downloaded from https://fedorapeople.org/groups/virt/...

Moreover, here are automated scripts to build Windows images: https://github.com/cloudbase/windows-...

Thanks.

Hello,

As the "unattend.xml" contains <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>, if the hypervisor hardware you are deploying to is different than the one where you generated the image, this leads to errors during the generalize step. If this is the case, you can remove this entry from the Unattend.xml.

If this is not the case, can you provide more information about your environment(hypervisor/os and cloudbase-init version used), so that we can try to reproduce the issue?

Thanks.

Hello,

First of all, if you use a nova key-pair to boot the machine, you can retrieve the user password by using "nova get-password <instance-id> <private-key-path>". If you use the Windows Server 2012 R2 trial image from our site, the default user is "Admin". The default user can be changed in the cloudbase-init.conf. If you use OpenStack, it is possible to post the password to the Openstack metadata service just once, thus if you run the plugin the second time, even if it will change the password, the first password will be available to nova.

Secondly, you can use the userdata-scripts(powershell, batch or other types) to execute your preferred password logic. If the exit code of the userdata script is 1002, the script will be executed at the next boot(re-executing the userdata plugin).

More information can be found here: http://cloudbase-init.readthedocs.org...

Thanks.

The admin password can be set by adding to the nova boot command "--meta admin_pass="MyStr@ngPass". When using the config drive metadata service, it is not possible to retrieve the password, unless http metadata is also enabled and used by cloudbase-init.

The config_drive image is created/managed by OpenStack nova. Cloudbase-init just uses the information inside it and does not/cannot manage it.

This branch adds support for the new virtio ISO folder structure, version higher than 0.1.8x: https://github.com/ader1990/windows-openstack-imaging-tools/tree/fix-virtio-iso

Hello,

The current windows-imaging-tools version has been tested with virtio drivers version lower than 0.1.8x. In case you are using an ISO with virtio drivers version higher then 01.8x: the issue is with the VirtIO driver ISOes, because since version 0.1.9x, the ISO has a different folder structure than the previous versions, leading to that error. I will submit asap a commit to handle this new scenario.

Thank you.

Hello,

I see in your neutron-hyperv-agent log an error: "Endpoint does not support RPC method tunnel_update". In case your neutron networks are gre/vxlan, Neutron hyperv agent does not support tunneling. You can only use flat/vlan network types. More details here: http://www.cloudbase.it/quantum-hyper...

If you need tunneling options, here is the information you need: http://www.cloudbase.it/open-vswitch-... .

Thanks.

For a working example, here is a working AD join performed by a PS script, when using HEAT. https://github.com/openstack/heat-templates/blob/master/hot/Windows/ActiveDirectoryController/ActiveDirectoryDomainController.ps1#L13

Hello there,

We already have this in place here: https://github.com/stackforge/cloudba...

Here are the exit codes:

• 1001 - reboot and don’t run the plugin again on next boot
• 1002 - don't reboot now and run the plugin again on next boot
• 1003 - reboot and run the plugin again on next boot

Please let me know if it works for you.

Great! I am glad it worked out.

Hello,

You have here some complete examples of Heat templates with PowerShell

https://github.com/openstack/heat-tem...

Hope it helps.

Hello, can you please paste the working script on http://paste.openstack.org/ or http://pastebin.com/? It is not working for me. Thanks.

Hello,

If you are using, for example, config-drive metadata service(which is read-only), the password cannot be exposed to the OpenStack backend and made available to the user.

As a suggestion to solve this issue, I suggest you to set a password for the instance in advance and in this case it doesn't need to be generated by cloudbase-init. You can find more details on how to set the password in this thread http://ask.cloudbase.it/question/317/...

Hope it works!

Hello,

First of all, with the latest changes in cloudbase-init code, some plugins have been moved to a new namespace. Make sure you have the appropriate plugins definition in your cloudbase-init.conf file. Latest code can be found here: https://github.com/stackforge/cloudba... . For example:

• cloudbaseinit.plugins.windows.sethostname.SetHostNamePlugin -> cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin

Secondly, I would suggest to use the cloudbase-init installer Sysprep option(without checking the automated Shutdown option), as it takes care of running cloudbase-init unattend. After you run sysprep, update the cloudbase-init.conf and cloudbase-init-unattend.conf according to your needs and shutdown the vm.

Hope it helps.

Hello,

If you have followed the tutorial you will have two files:

• key.pem
• key.pfx

You will need a private key file you can obtain by running this command:

openssl pkcs12 -in key.pfx -out private_key.pem -nodes

This is an example Python code to authenticate using a certificate: http://paste.openstack.org/show/197184/

The certificate authentication support has been included in pywinrm with this commit: https://github.com/diyan/pywinrm/comm...

Make sure you have the pywinrm version which contains this patch.

Hope it helps.

Hello, In order to reproduce this issue, can you provide some further information like how cloudbase-init was installed or if the metadata service provided a plain text password? Thanks.

Great! :)

Hello,

The password is used only if you explicitly set it when booting the vm. For example:

• nova boot --image image-id --meta admin_pass=p@ssw0rd vm-name

The password that is self-generated, the one from "adminPass" field, it is not taken into consideration by the metadata service, if it is not set when you create the server(boot the vm).

Hope it helps.

Hello,

This problem can be troubleshooted by checking the properties of your OpenStack networks.

If you use Neutron, you should check if the subnets in use have the proper DNS IPs set. In order to add a subnet with DNS, here is an example:

neutron subnet-create private 10.0.1.0/24 --dns_nameservers list=true 8.8.8.8

If you use nova-network, you can explicitly specify the DNS server that dnsmasq should use by setting the dns_server configuration option in /etc/nova/nova.conf. The following example would configure dnsmasq to use Google's public DNS server(link):

​dns_server=8.8.8.8

What is the metadata provider for Cloudbase-Init? For example, ConfigDrive does not support retrieving the password. To be sure, can you provide in a pastebin the Cloudbase-Initl og files? Thanks.

Hello,

Here is an example of an unattended cloudbase-init installation using the installer: https://github.com/cloudbase/windows-...

Furthermore, the parameters that you can specify are: USERNAME(string value), LOGGINGSERIALPORTNAME(string value), INJECTMETADATAPASSWORD(int value, accepted values: 0 or 1), NETWORKADAPTERNAME(string value).

For example:

msiexec -i $CloudbaseInitMsiPath /qn /l*v $CloudbaseInitMsiLog USERNAME=$username LOGGINGSERIALPORTNAME=$serialPortName INJECTMETADATAPASSWORD=1 NETWORKADAPTERNAME=$networkAdapterName

Hope it helps.

Hi,

"rem" command is used to put a comment in a batch file

A valid command script would be:

rem cmd

start "C:\Program Files\Internet Explorer" IEXPLORE.EXE www.google.com

You should also take into consideration that the user-data script is ran under the user cloud-init.

Hope it helps.

Hello,

In order to take a better look at this issue, can you provide the cloudbase-init log file and the example outputs of nova get-password?

Make sure you use the latest version of Cloudbase-Init as there was an issue with the passwords, which had been recently solved(on the 5th of January).

Thanks.

Hello,

First of all, m1.tiny is too small for a Windows vm. m1.small or higher(at least 32GB) is preferable.

Secondly, when you create the Windows image you can specify a property: --property hypervisor_type=hyperv, in order for the nova scheduler to choose the correct compute node. More info on creating the image you can find here: http://www.cloudbase.it/filtering-gla...

For more debugging, you can take a look at: nova service-list, to check if all the nodes are up.

Hope it helps.

If this does not work, you can examine the windows error log (start eventvwr.msc). Moreover, you can give some details about the information you have inserted when you have installed the msi and the features you have enabled. Thanks.

You can try adding a & when running: & "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\Python27\Scripts\nova-compute.exe" --config-file "C:\Program Files (x86)\Cloudbase Solutions\OpenStack\Nova\etc\nova.conf". The log folder is "C:\OpenStack\Log".

Hello, There is a problem with the string escaping when setting the user password. I have opened a bug on launchpad(here) and I'll come back with a bug fix asap.

Thanks for the notice.

During the install process we are setting the registry key HKLM\System\Setup!UnattendFile with the value "<cloudbase-init config="" folder="">\Unattend.xml", in order to make sure the cloudbase-init unattend file has the highest priority and to avoid a short path issue. That may be the problem and we are checking now. to confirm/fix this issue.

In the mean time, you could copy your AnswerFile from $LocalUnattendFile to "<cloudbase-init config="" folder="">\Unattend.xml" and try to run "$ENV:SystemRoot\System32\Sysprep\Sysprep.exe" /generalize/oobe /shutdown again, that should work and get your environment working as expected.

In order to know what answer file is used, can you post the contents of these files? C:\Windows\Panther\setupact.log C:\Windows\Panther\UnattendGC\setupact.log

As you cannot attach files and there is no formatting on the comments, I'd suggest pastebin.com or paste.openstack.org .

Thanks.