Skip to main content

AWS Cloud9

Development has stepped into 2017 and there is no better time to have the flexibility of development and shared coding like AWS Cloud9.

One of the best challenges during any development and merging code and seeing what someone wrote and fixing their mistakes or sharing information if you need help fixing something. There is no greater joy than doing this in real-time. It's also a way to monitor development activities of contract or freelance developers.

In times past, if you weren't writing the application yourself, you paid, gave requirements and then developers would send you back a project without fully understanding what was done. With AWS Cloud9, this becomes a legacy problem that is now fixed.

Since AWS has thrown their weight behind their recent purchase of AWS Cloud9, this should be very exciting to comes of the shared collaborations on Open Source or even Blockchain projects with the advent of AWS Cloud9 and true shared coding capabilities.

After launching the platform, it's extremely easy to use. The complexity of the old platform is gone and it's a joy to use!

https://aws.amazon.com/cloud9/ 

Popular posts from this blog

How to Fix /storage/core filesystem Out of Disk Space Error on VCSA 6.0U1

How to fix the error of "The /storage/core filesystem is out of disk space or inodes"


Step 1: Login to the new VCSA 6.0U1 HTML5 web client. https://ip address:5480



Step 2: Enable SSH and Bash Shell
Step 3: Login as root and type "shell" at Command> shell
Step 4: df -h (Check if it's out of space)
/dev/mapper/core_vg-core               50G   50G     0 100% /storage/core
Step 5: Stop the services of VCSA: 
hostname: # service vmware-vpxd stop hostname: # service vmware-vpxd status (make sure it is stopped)
Step 6:  cd /storage/core
Step 7: rm -rf *.tgz (be CAREFUL...do this in the wrong directory and you will be retrieving from a backup.)


If you need help. Go to Cybercity (http://www.cyberciti.biz/faq/delete-all-files-folder-linux/
Step 8: service vmware-vpxd restart

Step 9: history -c
Step 10: Refresh the browser (https://ip address:5480). Now it's all green


VMware KB: (

How to Configure HP ILO 4 for Active Directory Login

1. Make sure that your Windows Active Directory Domain Controller has an SSL Certificate to support port 636 (HP's authentication doesn't like 389)

2. Use Softerra LDAP Administrator (or whatever is your preferred tool to get the OU path) if you don't know how to do it by heart (which...um...sometimes its better to verify).

3. Make sure that you have a way to authenticate users by adding in the OU where your restricted accounts are located. You don't want anyone in the domain to be able to login to the server.

ILO Login > Administration > User Administration - Click New and Add the Group DN Only:



Click Add Group and then you will see your group added. (*Make sure it's a security group)


4. Add in your Windows Active Directory DC to authenticate against (Verified against 2008R2):

ILO Login > Administration > Security - Directory (*Make sure it's the OU where the security group is)


5. Sign Out (Log off) and then Log Back in (If you don't see Direct…

VCSA vmware-vpxd Service Won't Restart After Upgrading to 6.0 U2

You navigate to the VMware Web Client and you get this 503 Error:
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x7fe4a805cc90] _serverNamespace = / _isRedirect = false _pipeName =/var/run/vmware/vpxd-webserver-pipe)
Cause:(SSL Certificates wouldn’t issue automatically after reboot for service vmware-vpxd
Compounded Problem:(Clearing logs under ~/.* **root**) – Specifically, clearing ~/.pgpass 
(Lesson Learned: NEVER EVER CLEAR FILES UNDER ~/. Except .bash_history on templates creation only!!!)
Fix: Kill all the services running vpxd
1. ps -ef | grep vpxd 2. kill ### 3. Re-add the ~/.pgpass file with the PostGreSQL password 4. vi /et c/vmware-vpx/embedded_db.cfg 5. Copy the password you see between PGUSER_PASSWORD=’password here‘ 6. Put the password back in ~/.pgpass
localhost:5432:VCDB:postgres: password here localhost:5432:postgres:postgres: password here localhost:5432:VCDB:vc: password here
7. Check /etc/hosts and make sure config is there. 10.…