Skip to content
This repository has been archived by the owner on Jul 29, 2018. It is now read-only.

ADB 2.0.0 release tracker issue #363

Closed
navidshaikh opened this issue Apr 22, 2016 · 9 comments
Closed

ADB 2.0.0 release tracker issue #363

navidshaikh opened this issue Apr 22, 2016 · 9 comments

Comments

@navidshaikh
Copy link
Contributor

navidshaikh commented Apr 22, 2016

The issue to be used to enlist the fixes and enhancement as well as for testing.

@navidshaikh
Copy link
Contributor Author

Add changelog for #352

@LalatenduMohanty
Copy link
Contributor

LalatenduMohanty commented Apr 25, 2016

Latest Build:

https://cbs.centos.org/koji/taskinfo?taskID=87014 (It have latest adb-utils 1.5 version i.e. latest)

Check the Chenagelog to see changes in the build : https://github.com/projectatomic/adb-atomic-developer-bundle/blob/master/CHANGELOG.md#unreleased

Notable change is adding openshift2nulecule to the box

Old Builds

@LalatenduMohanty
Copy link
Contributor

Kubernetes setup and sudo -E atomic run projectatomic/helloapache works fine

@LalatenduMohanty
Copy link
Contributor

@dharmit can you please check the mesos setup?
@kadel Can you please check if o2n is working in the box? o2n is by pre-installed the box.

@LalatenduMohanty
Copy link
Contributor

OpenShift through the Vagrantfile works fine


[vagrant@centos7-adb ~]$ oc new-app nodejs-example
--> Deploying template nodejs-example in project openshift for "nodejs-example"
     With parameters:
      Memory Limit=512Mi
      Git Repository URL=https://github.com/openshift/nodejs-ex.git
      Git Reference=
      Context Directory=
      Application Hostname=
      GitHub Webhook Secret=YM6lgtHdxrvowcb0kmBbCyF3M02wgNF3WPgseuE7 # generated
      Generic Webhook Secret=oGiuQXPnanC6g2DWwCEMJNH6RAhVgVBSJ7x6SKhG # generated
      Database Service Name=
      MongoDB Username=
      MongoDB Password=
      Database Name=
      Database Administrator Password=
--> Creating resources with label app=nodejs-example ...
    Service "nodejs-example" created
    Route "nodejs-example" created
    ImageStream "nodejs-example" created
    BuildConfig "nodejs-example" created
    DeploymentConfig "nodejs-example" created
--> Success
    Build scheduled for "nodejs-example" - use the logs command to track its progress.
    Run 'oc status' to view your app.


[vagrant@centos7-adb ~]$ oc logs dc/nodejs-example
I0427 05:52:35.064856       1 deployer.go:196] Deploying sample-project/nodejs-example-1 for the first time (replicas: 1)
I0427 05:52:35.066167       1 recreate.go:105] Scaling sample-project/nodejs-example-1 to 1 before performing acceptance check
I0427 05:52:37.109856       1 recreate.go:110] Performing acceptance check of sample-project/nodejs-example-1
I0427 05:52:37.109979       1 lifecycle.go:391] Waiting 600 seconds for pods owned by deployment "sample-
project/nodejs-example-1" to become ready (checking every 1 seconds; 0 pods previously accepted)


[vagrant@centos7-adb ~]$ oc status
In project OpenShift sample project (sample-project) on server https://127.0.0.1:8443

svc/nodejs-example - 172.30.122.2:8080
  dc/nodejs-example deploys imagestreamtag/nodejs-example:latest <-
    bc/nodejs-example builds https://github.com/openshift/nodejs-ex.git with openshift/nodejs:0.10 
    #1 deployed 4 minutes ago - 1 pod
  exposed by route/nodejs-example

View details with 'oc describe <resource>/<name>' or list everything with 'oc get all'.

@LalatenduMohanty
Copy link
Contributor

Vagrant-service-manager following commands works fine

[root@dhcp35-203 centos-openshift-setup]# vagrant service-manager env
Configured services:
docker - running
openshift - running
kubernetes - stopped

docker env:
# Set the following environment variables to enable access to the
# docker daemon running inside of the vagrant virtual machine:
export DOCKER_HOST=tcp://10.1.2.2:2376
export DOCKER_CERT_PATH=/home/ADB200_rc3/adb-atomic-developer-bundle/components/centos/centos-openshift-setup/.vagrant/machines/default/libvirt/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.21
# run following command to configure your shell:
# eval "$(vagrant service-manager env docker)"

openshift env:
You can access the OpenShift console on: https://10.1.2.2:8443/console
To use OpenShift CLI, run: oc login https://10.1.2.2:8443
[root@dhcp35-203 centos-openshift-setup]# vagrant service-manager env docker
# Set the following environment variables to enable access to the
# docker daemon running inside of the vagrant virtual machine:
export DOCKER_HOST=tcp://10.1.2.2:2376
export DOCKER_CERT_PATH=/home/ADB200_rc3/adb-atomic-developer-bundle/components/centos/centos-openshift-setup/.vagrant/machines/default/libvirt/docker
export DOCKER_TLS_VERIFY=1
export DOCKER_API_VERSION=1.21
# run following command to configure your shell:
# eval "$(vagrant service-manager env docker)"
[root@dhcp35-203 centos-openshift-setup]# vagrant service-manager env openshift
You can access the OpenShift console on: https://10.1.2.2:8443/console
To use OpenShift CLI, run: oc login https://10.1.2.2:8443
[root@dhcp35-203 centos-openshift-setup]# vagrant service-manager env openshift --script-readbale
Usage: vagrant service-manager env [object] [options]

Objects:
      docker      display information and environment variables for docker
      openshift   display information and environment variables for openshift

If OBJECT is ommitted, display the status of all services and information
for all active services

Options:
      --script-readable  display information in a script readable format.
                         Only supported by the openshift object.
      -h, --help         print this help
[root@dhcp35-203 centos-openshift-setup]# vagrant service-manager env openshift --script-readable
OPENSHIFT_URL=https://10.1.2.2:8443
OPENSHIFT_WEB_CONSOLE=https://10.1.2.2:8443/console

@dharmit
Copy link
Contributor

dharmit commented Apr 27, 2016

@LalatenduMohanty Mesos Vagrantfile works well. I was able to start the box and deploy helloapache atomicapp inside it on Marathon. Do you need me to do any more checking on this?

@LalatenduMohanty
Copy link
Contributor

@dharmit that should be enough. Thanks

@LalatenduMohanty
Copy link
Contributor

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants