walmartlabs / walmart-cla Goto Github PK

I deployed it on a test account and followed the deploy with the test assembly and I noticed in the logs that it was running queries on currently running instances.

Why is it doing that, and will it modify existing infrastructure that isn't configured somewhere in oneops?

Please correct the following errors:

Error updating database. Cause: org.postgresql.util.PSQLException: ERROR: Date out of range. Fix the cm_ci_log_insert() function! Where: SQL statement "insert into cm_ci_log(log_id, log_time, log_event, ci_id, ci_name, class_id, class_name, comments, ci_state_id, ci_state_id_old) values ...

I have created a openstack cloud following these instructions: http://oneops.github.io/user/howto/#add-a-new-cloud however when it comes to enabling the platform for deployment I get the error message that I am missing the service:
dns, gdns.
The documentation isn't very clear on this or even where I can set these settings.

As a developer, what's the API to use to implement cost management module which is mentioned oneops link i.e http://oneops.com/user/account/cost-management

What's I have to configure in Java as well as in UI implementation using Ruby on Rails.

It we be great helpful if any documentation reference provided.

Thanks.

We have to create a contact information for feedback (or) issues, Other than slack.

Hi,

I am actually trying to install OneOps installation on Centos 7 bypassing vagrant. So the steps which I followed was after cloning the setup from vagrant-centos7.
After the installation, I executed oo-setup.sh but it gets stuck at waiting for jenkins to come online.

Need some help.

This issue is created to notify everyone in the walmartlabs and walmart github organizations about the activation of CLA assistant.

Please review the information on the walmart internal website https://sde.walmart.com/blog/2018-01-22-cla-made-easy.html
as well as the readme of this repository.

Notification to all members will go out via github notifications and CLA assistant will be activated shortly.

Hi All,

I hope if we add cloudstack / Docker management / Digital Ocean / Softlayer will be great in the upcoming OneOps

2016-01-28T21:53:57+00:00] DEBUG: backtrace entry for compile error: '/opt/oneops/inductor/circuit-oneops-1/components/cookbooks/compute/recipes/add_node_ec2.rb:147:in `exit''

[2016-01-28T21:53:57+00:00] DEBUG: Line number of compile error: '147'

[31mRecipe Compile Error in /opt/oneops/inductor/circuit-oneops-1/components/cookbooks/compute/recipes/add.rb�[0m

Trying to deploy SimpleApache on EC2

Please correct the following errors:

Error updating database. Cause: org.postgresql.util.PSQLException: ERROR: Date out of range. Fix the cm_ci_log_insert() function! Where: SQL statement "insert into cm_ci_log(log_id, log_time, log_event, ci_id, ci_name, class_id, class_name, comments, ci_state_id, ci_state_id_old) values ...

• https://sde.walmart.com/docs/open-source/index.html
• https://sde.walmart.com/

Kindly add the necessary services for OpenStack deployment

Hi,

I have been having this problem whenever i try to install oneops with Vagrant, need help:

==> default: Downloading jenkins war: http://mirror.xmission.com/jenkins/war-stable/1.642.1/jenkins.war
==> default: Can not instal jenkins, exiting :-(

this is just a test -- ignore

Here is the output from the terminal:

brians-MacBook-Pro:vagrant-centos7 brianrountree$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'box-cutter/centos72'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'box-cutter/centos72' is up to date...
==> default: Setting the name of the VM: oneops
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 3001 (guest) => 3003 (host) (adapter 1)
default: 3000 (guest) => 9090 (host) (adapter 1)
default: 8161 (guest) => 8166 (host) (adapter 1)
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

Kindly add the necessary services for OpenStack deployment

Testing

I had three instances running in a cluster How to forcefully remove an instance from the production environment so that other two are running and mean while we make changes to the instance and again up the process in order decrease the maintenance of production time and so on for other two instances too.

For any platform I create for the Openstack cloud, I am getting failed deployments at the sshKeys component level (step 1 in the deployment plan).
I can't modify the component to add any ssh keys, and pressing repair (as the admin) gives me unauthorized access.
Here is the error output I see from the deployment plan logs

[2016-03-30T02:10:06+00:00] ERROR: no implicit conversion of nil into String
[2016-03-30T02:10:06+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
[2016-03-30T02:18:17+00:00] FATAL: Stacktrace dumped to /tmp/chef-stacktrace.out
[2016-03-30T02:18:17+00:00] ERROR: Running exception handlers
[2016-03-30T02:18:17+00:00] ERROR: Exception handlers complete

Hi,

This is not a bug.

I was going through the API Documentation and wasn't able to clearly understand how the API works in OneOps. Basically the complete workflow of how oneops API works.

Need help in this regard.

Thanks