Installing Nimbus -cont.

1. Tim answered me that I can shutdown the domain and the state will be unchanged. So let's check it out. However, I doubt since every time I load the image then I have to modify the password. So let's see if Tim is right.
The 'xm save' saves the ram.

And the answer is yes. Tim is right.

2. Since the domain is based on dhcp-ip so it changes every time the domain
is instantiated so I need to do this bi-directional password-less ssh stuff again.
And this is the good brief tutorial to do that.

3. However, I got again the same error with pseudoterminal:

magg@gobo:~/.ssh$ ssh magg@h973c
PTY allocation request failed on channel 0

So I came back to my previous post. It occurs that /dev/pts is missing so I created it and mounted. And that was enough:

h973C:/home/magg# mkdir /dev/pts
h973C:/home/magg# mount /dev/pts

4. So now we need to refresh the globus certificates and I can try to install the nimbus.


BUILD SUCCESSFUL
Total time: 23 seconds
Successful: Nimbus - build and install all
magg@gobo:~/nimbus/nimbus-TP2.2$

5. It looks that I need passwordless auth from gobo to gobo.

6. This autoconfig.sh script requires that the workspace control should be installed. So now I tried to install this workspace control. So I need to download
and install this nimbus-controlled.tgz

7. Create a necessary directory structure. You can try to run this with the
option '-o' for the first time instead of '-i'

gobo:/home/magg/nimbus/nimbus-controls-TP2.2/workspace-control# python install.py -c /opt/workspace/worksp.conf -a magg -g magg -i

Then try to change something. I change the below files before installation so
the changes were copied to the /opt/workspace/blah blah


DHCPD_CONF dhcp-config.sh

gobo:/home/magg/nimbus/nimbus-controls-TP2.2/workspace-control# cp dhcp-config.sh dhcp-config.sh.org
gobo:/home/magg/nimbus/nimbus-controls-TP2.2/workspace-control# nano dhcp-config.sh

DHCPD_CONF="/etc/dhcp3/dhcpd.conf"

8. copying images

gobo:/home/magg/nimbus/nimbus-controls-TP2.2/workspace-control# cp /home/xen/domains/hello-cloud/hello-cloud.* /opt/workspace/images/

gobo:/home/magg/nimbus/nimbus-controls-TP2.2/workspace-control# cp /opt/workspace/worksp.conf /opt/workspace/worksp.conf.org

gobo:/home/magg/nimbus/nimbus-controls-TP2.2/workspace-control# nano /opt/workspace/worksp.conf

guestkernels: /opt/workspace/images/hello-cloud.img,%(localdir)s/vmlinuz-2.6-xen

9. testing

gobo:/home/magg/.ssh# cp /home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/share/nimbus-clients/sample-workspace.xml /home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/share/nimbus-clients/sample-workspace.xml.org

nano sample-workspace.xml:

file://hello-cloud.img

I have got some errors:

gobo:/home/magg/nimbus# ./test-create.sh

Workspace Factory Service:
https://127.0.0.1:8443/wsrf/services/WorkspaceFactoryService

Read metadata file: "/home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/share/nimbus-clients/sample-workspace.xml"
Created deployment request soley from arguments.

Creating workspace "http://example1/localhost/image"...
Problem: General error: ; nested exception is:
GSSException: Defective credential detected [Caused by: Proxy file (/tmp/x509up_u0) not found.]

9a. So I run the container and created this certificates - proxy or whatever. And run as a magg user. I have got the following error:

magg@gobo:~/nimbus$ ./test-create.sh

Workspace Factory Service:
https://127.0.0.1:8443/wsrf/services/WorkspaceFactoryService

Read metadata file: "/home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/share/nimbus-clients/sample-workspace.xml"
Created deployment request soley from arguments.

Creating workspace "http://example1/localhost/image"...
Problem: General error: org.globus.wsrf.impl.security.authorization.exceptions.AuthorizationException: "/C=f56baae7-1024-4c02-951c-3c9466917c37/CN=ms" is not authorized to use operation: {http://www.globus.org/2008/06/workspace}create on this service
magg@gobo:~/nimbus$

9b. magg@gobo:~/nimbus$ nano /home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/etc/nimbus/nimbus-grid-mapfile
"/C=f56baae7-1024-4c02-951c-3c9466917c37/CN=ms" fakeaccount

9c. now the test script worked

10. Continuing nimbus script:
---------------------
These settings are now stored in '/home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/share/nimbus-autoconfig/autoconfig-decisions.sh'

If you type 'y', that script will be run for you with the settings.

Or you can answer 'n' to the next question and adjust this file.
And then manually run '/home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/share/nimbus-autoconfig/autoconfig-adjustments.sh' at your leisure.

OK, point of no return. Proceed? y/n
--------------------
After pressing the 'y':

----------------------------------------
NOTE: you need to MATCH this network in the workspace-control configuration file.
This configuration file is at '/opt/workspace/worksp.conf' by default

For example, you might have this line:

association_0: public; xenbr0; vif0.1 ; none; 170.149.151.54/24

... "public" is the name of the network we chose.
... "xenbr0" is the name of the bridge to put VMs in this network on.
... "vif0.1" is the interface where the DHCP server is listening in dom0 on the VMM
... and the network address range serves as a sanity check (you can disable that check in the conf file)

----------

Making sure 'fake mode' is off:

[*] The 'fake.mode' configuration was:
... set to 'false'
... (it used to be set to 'true')
... in the file '/home/magg/nimbus/autocontainer/gt/ws-core-4.0.8/etc/nimbus/workspace-service/other/common.conf'

----------

Finished.

See 'NOTE' above.
--------------------------------

11. Following the instructions from the web page I obtained the expected results. So it looks as it works. Check the security and map-grid-something files.