sfc-gh-eraigosa
commented
8 years ago Hey, lots of questions, thats fantastic! OK, let me try to answer, let me know if i missed a question.
- How can i target a specific blade. Today we don't allow for you to pick a blade by serial or anything like that, but what you can do is assign a profile name to a blade prior to running docker-machine. If docker-machine plugin finds a blade with that name, then it will use it.
- How do i use the plugin.
Just like any other plugin, place the
docker-machine-driver-oneviewin the system path, or same folder as the docker-machine executable. Then include the option--driver oneview. Running the commanddocker-machine --driver oneview createshould produce output that comes from the oneview executable and confirms the plugin is talking to docker-machine.
Here is an example command that works for me well:
cat > credentials_andsettings.env << EOF
export ONEVIEW_APIVERSION=200
# you need this so we can create and join a new server to ICSP
# if the server already exist in ICSP we don't provision it
export ONEVIEW_ILO_USER=user
export ONEVIEW_ILO_PASSWORD=password
export ONEVIEW_ICSP_ENDPOINT=https://icsp.yournet.com
export ONEVIEW_ICSP_USER=user
export ONEVIEW_ICSP_PASSWORD=password
export ONEVIEW_ICSP_DOMAIN=domain
export ONEVIEW_OV_ENDPOINT=https://oneview.yournet.com
export ONEVIEW_OV_USER=user
export ONEVIEW_OV_PASSWORD=password
export ONEVIEW_OV_DOMAIN=domain
export ONEVIEW_SSLVERIFY=true
export ONEVIEW_SERVER_TEMPLATE=oneviewtemplate
export ONEVIEW_OS_PLAN="icsp build plan"
# if you have a proxy for your data center
export proxy_enable=true
export proxy_config='http_proxy=http://proxy.yournet.com:8080/
https_proxy=https://proxy.yournet.com:8080/
no_proxy=/var/run/docker.sock,.proxy.yournet.com,localhost,127.0.0.1'
# proxy settings for --engine-evn options
export http_proxy=http://proxy.yournet.com:8080/
export https_proxy=https://proxy.yournet.com:8080/
export no_proxy=/var/run/docker.sock,.proxy.yournet.com,localhost,127.0.0.1
EOF
source credentials_adnsettings.env
# add the --engine-env options if you have a proxy
docker-machine create \
--oneview-os-plan "${ONEVIEW_OS_PLAN}" \
--oneview-server-template "${ONEVIEW_SERVER_TEMPLATE}" \
--oneview-public-connection-name "Name_of_public_network" \
--driver oneview \
--engine-env HTTP_PROXY="$http_proxy" \
--engine-env HTTPS_PROXY="$https_proxy" \
--engine-env NO_PROXY="$no_proxy" \
--engine-env http_proxy="$https_proxy" \
--engine-env https_proxy="$https_proxy" \
--engine-env no_proxy="$no_proxy" \
nodename- Why do we have to use ilo user/password
This was needed to add a server to icsp. If we see that the server is already in icsp, we don't want to add it to docker-machine or provision it, to avoid destroying someone else server that might have already been provisioned. This way docker-machine always tries to add the new server to icsp (it should not exist in icsp prior to a create command).
Do let us know your progress and issues so we can make it easier.
ddefolo
anandgagrani
In the docker-machine create command (for oneview with docker) how do you specify which blade to use in the oneview infrastructure, for the docker host provision? I would like to provision host on specific blade but in the example command set below..there is no option to specify target blade. Also how to use the docker with oneview plugin...there is no clear document defining all the steps. if you can answer this question ..I am almost done with creating one document for everyone.
docker-machine create \
--engine-env HTTP_PROXY="" \ --engine-env HTTPS_PROXY="" \ --engine-env NO_PROXY="" \ --driver oneview \ --oneview-os-plan "RHEL71_DOCKER_18"\ --oneview-server-template "SP_template" \ --oneview-ov-user=Administrator \ --oneview-ov-password=\ --oneview-ov-domain=\ --oneview-ov-endpoint=https://15.xx.xx.xx/ \ --oneview-icsp-user=administrator \ --oneview-icsp-password=\ --oneview-icsp-endpoint=15.215.xx.xx\ --oneview-ssh-user=administrator \ --oneview-ilo-user=administrator \ --oneview-ilo-password=\ docker-ip-node-01
Also what does this mean: Name: "oneview-ilo-user",
Usage: "ILO User id that is used during ICSP server creation.",
I do not remember using any ilo when creating ICSP vm and then its template.
I am following the steps mentioned in document below(that is rather vague in actual steps) https://h20195.www2.hp.com/V2/getpdf.aspx/4AA6-2595ENW.pdf