Comments

• 

  about 10 years ago by markkp | Reply

  I was (eventually) successful in getting most things to work. The one thing I could not accomplish was to perform an actual install of SLES on the compute node. The install would start, but then sit there, seemingly forever, chewing up 100% of the virtual processors assigned to the guest. What was interesting about this was that I could boot the system into rescue mode from the same DVD image with no problems. I'm guessing that running this as a guest on a compute node that was already a KVM guest of my workstation either ran into performance problems or the hardware detection part of the installer had some sort of problem due to the nesting.

  Aside from that, I found it very frustrating to try and figure out the networking, and how things should be set up, even by default. I had tried to start off by reading the deployment guide, but with that being over 200 pages long, I figured that I would never finish that before the end of the week.

  Things wouldn't have been so bad if it would have been possible to re-deploy the admin node without having to re-install the whole operating system.

×
Edit Comment 900
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
I was (eventually) successful in getting most things to work. The one thing I could not accomplish was to perform an actual install of SLES on the compute node. The install would start, but then sit there, seemingly forever, chewing up 100% of the virtual processors assigned to the guest. What was interesting about this was that I could boot the system into rescue mode from the same DVD image with no problems. I'm guessing that running this as a guest on a compute node that was already a KVM guest of my workstation either ran into performance problems or the hardware detection part of the installer had some sort of problem due to the nesting. Aside from that, I found it very frustrating to try and figure out the networking, and how things should be set up, even by default. I had tried to start off by reading the deployment guide, but with that being over 200 pages long, I figured that I would never finish that before the end of the week. Things wouldn't have been so bad if it would have been possible to re-deploy the admin node without having to re-install the whole operating system.
 
×
Reply to markkp
I was (eventually) successful in getting most things to work. The one thing I could not accomplish was to perform an actual install of SLES on the compute node. The install would start, but then sit there, seemingly forever, chewing up 100% of the virtual processors assigned to the guest. What was interesting about this was that I could boot the system into rescue mode from the same DVD image with no problems. I'm guessing that running this as a guest on a compute node that was already a KVM guest of my workstation either ran into performance problems or the hardware detection part of the installer had some sort of problem due to the nesting.
Aside from that, I found it very frustrating to try and figure out the networking, and how things should be set up, even by default. I had tried to start off by reading the deployment guide, but with that being over 200 pages long, I figured that I would never finish that before the end of the week.
Things wouldn't have been so bad if it would have been possible to re-deploy the admin node without having to re-install the whole operating system.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  about 10 years ago by markkp | Reply

  Other parts of the install/configuration were also confusing. My general impression is that a paying customer is likely going to require a consultant to help them get things set up unless they already have someone with reasonable OpenStack experience on staff.

×
Edit Comment 902
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Other parts of the install/configuration were also confusing. My general impression is that a paying customer is likely going to require a consultant to help them get things set up unless they already have someone with reasonable OpenStack experience on staff.
 
×
Reply to markkp
Other parts of the install/configuration were also confusing. My general impression is that a paying customer is likely going to require a consultant to help them get things set up unless they already have someone with reasonable OpenStack experience on staff.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview