thecodeteam / roadmap

The {code} Team Roadmap
3 stars 1 forks source link

Review and test existing RackHD deployment #106

Closed clintkitson closed 8 years ago

clintkitson commented 8 years ago

We will be acting as the consumers for the RackHD project where we focus on ensuring a seamless deployment of RackHD.

clintkitson commented 8 years ago

In process. Deploying with vagrant is good, getting stuck on a step for building boot images.

clintkitson commented 8 years ago

Looking good now on deployment. Waiting for steps for actually deploying something with RackHD that is useful as an example.

kacole2 commented 8 years ago

@clintonskitson same here. was successfully able to boot up the Vagrant "monorail" server and all services come up as expected. Following the quick start, I can power on a pxe-1 but it's left with a "no image found" after boot up. There needs to be some documentation on building a proper JSON file or whatever needs to be done next for a quick start. This would round out everything.

8. Development Guide should probably be renamed to something like Administrator Guide or User Guide. Using Development Guide makes it seem like you are going to start trolling through the internal code.

I'm trying to perform some of the commands on the host but not receiving any replies

curl http://172.31.128.1:8080/api/1.1/workflows/library
curl: (52) Empty reply from server
clintkitson commented 8 years ago

You can also one Joe in the Rackhd channel in the community for the latest or if you have suggestions.

On Wednesday, November 25, 2015, Kendrick Coleman notifications@github.com wrote:

@clintonskitson https://github.com/clintonskitson same here. was successfully able to boot up the Vagrant "monorail" server and all services come up as expected. Following the quick start, I can power on a pxe-1 but it's left with a "no image found" after boot up. There needs to be some documentation on building a proper JSON file or whatever needs to be done next for a quick start. This would round out everything.

  1. Development Guide should probably be renamed to something like Administrator Guide or User Guide. Using Development Guide makes it seem like you are going to start trolling through the internal code.

I'm trying to perform some of the commands on the host but not receiving any replies

curl http://172.31.128.1:8080/api/1.1/workflows/library curl: (52) Empty reply from server

— Reply to this email directly or view it on GitHub https://github.com/emccode/roadmap/issues/106#issuecomment-159638495.

kacole2 commented 8 years ago

ahh. good call

heckj commented 8 years ago

or you can @heckj mention me here and I'll respond. It is open source after all :-)

clintkitson commented 8 years ago

Exactly =)

On Thursday, December 3, 2015, Joseph Heck notifications@github.com wrote:

or you can @heckj https://github.com/heckj mention me here and I'll respond. It is open source after all :-)

— Reply to this email directly or view it on GitHub https://github.com/emccode/roadmap/issues/106#issuecomment-161665917.