I have just bought a Siera Wireless 320U (from Telstra) and have had good success with it in a RB751G-2HnD running routeros 5.20. I am not in a LTE coverage area so have not tried this in Direct IP/LTE mode but it works fine for 3G. When you plug the 320U into the routerboard it should appear as `USB2.
- Create a new PPP session
- Select “usb2”
- set “Data Channel” to 3
- set “Info Channel to 4.
- set APN to “telstra.internet” (or whatever is appropriate for your plan/carrier)
- set the username and password
- if you have a pin set on your SIM then set this too (I have not tested this with a PIN)
- Under the PPP tab, make sure to de-select “Dial On Demand”
- Leave all the other settings as default.
You should now have a new interface that can connect to 3G. Don’t forget to setup NAT for this new interface.
Just switched from my iPhone 4s to != iPhone5.
So first (geek) question is:
how do I telnet?
The somewhat unexpected answer to me was Telnet IDE. It is a very natural implementation of a terminal. You just get a reduced shell on your android, but the really nice feature is the keyboard. You enable the keyboard under Settings->My Device->Language and Input. Just select Terminal IDE as your input and you will get all the keys you are missing. Like alt, arrows, ctrl etc.
So… now if you have your free instance in Amazon that I wrote about earlier. You want to ssh to that instance with your android? It turned out to be a bit of work….
I think this is the easy (ish) way.
Since you already have 50 gig on dropbox (if you registered your galaxy), might as well use it.
If you are using ubuntu in AWS, go ahead and add your dropbox repository with your normal way of ssh’ing to it:
with the following:
deb http://linux.dropbox.com/ubuntu precise main
do the usual with apt-get update etc… apt-get install dropbox
oh and do install the key that get printed out as well:)
apt-key adv --keyserver php.mit.edu --recv-keys <key>
when you do dropbox start it does want you to add the host in dropbox. You can do that on your local laptop since you probably don’t have X installed in the AWS cloud.
Restart dropbox and you should have a Dropbox directory replicating your data!
Now you can get stuff from your phone to the AWS instance without effort:)
so we need a ssh key to use with amazon. To create the key on your android:
open a terminal in TerminalIDE and:
dropbearkey -t rsa -f ~/.ssh/id_rsa
Now you have the key. Let’s add it to AWS.
Generate the ascii version of the key
dropbearkey -y -f ~/.ssh/id_rsa >/storage/sdcard0/files/id_rsa.txt
Now you can upload it with your dropbox app on the phone. Go to upload and browse to “Other Files”->”Internal Storage”->”files”
So now go ahead and ssh to your aws host. The file should be in your ~/Dropbox/ directory. Then just
cat id_rsa.txt >>~/.ssh/authorized_keys
Now you can ssh with telnetIDE:
ssh firstname.lastname@example.org -i id_rsa
Nice press-release by AMD on what we done together on the Seamicro platform.
I’ve not had a good introduction to MCollective slide deck ever, I usually just give demos and talk through it. I was invited to talk in San Francisco about MCollective so made a new deck for this talk.
On the night I gave people the choice of talks between the new Introduction talk and the older Managing Puppet using MCollective and sadly the intro talk lost out.
Last night the excellent people at Workday flew me to Dublin to talk to the local DevOps group there and this group was predominantly Chef users who chose the Introduction talk so I finally had a chance to deliver it. This talk was recorded, hopefully it’ll be up soon and I’ll link to it once available.
This slide deck is a work in progress, it’s clear I need to add some more information about the non-cli orientated uses of MCollective but it’s good to finally have a deck that’s receiving good feedback.
We uploaded the slides back when I was in San Francisco to slideshare and those are the ones you see here.
The word “DevOps” has been thrown around quite a lot lately. Job boards are awash with requisitions for “DevOps Engineers” with varying descriptions. What is DevOps, really?
In order to better under what the fuss is all about, we surveyed 620 engineers to examine what they do to keep everything running like clockwork – from day-to-day activities, key processes, tools and challenges they face. The survey asked for feedback on how much time is spent improving infrastructure and setting up automation for repetitive tasks; how much time is typically spent fighting fires and communicating; and what it takes to keep the lights on. We then compared responses belonging to those from traditional IT and DevOps teams. Here are the results, in time spent each week carrying out key activities:
Conclusions we can draw from the results
DevOps oriented teams spend slightly more time automating tasks
Writing scripts and automating processes have been a part of the Ops playbook for decades now. The likes of shell scripts, Python and PERL, are often used to automate repetitive configuration tasks but with the newer tools like Chef and Puppet, Ops folk perform more sophisticated kinds of automation such as spinning up virtual machines and tailoring them to the app’s needs using Chef or Puppet recipes.
Both Traditional IT and DevOps oriented teams communicate actively
Respondents belonging to a DevOps oriented team spend 2 fewer hours communicating each week, possibly because DevOps fosters better collaboration and keeps Dev and Ops teams in sync with each other. However, Dev and Ops folk in Traditional IT teams spend over 7 hours each week communicating. This active dialogue helps them better understand challenges, set expectations and triage issues. How much of this communication can be deemed inefficient is subjective, but it is necessary to get both teams to onboard. Today, shared tooling, instant messaging, task managers and social tools also help bring everyone closer together in real-time.
DevOps oriented teams fight fires less frequently
A key tenet of the DevOps methodology is to embrace the possibility of failures, and be prepared for it. With alerts, continuous testing, monitoring and feedback loops that expose vulnerabilities and key metrics, teams are enabled to act quickly and proactively. Programmable infrastructure and automated deployments provide a quick recovery while minimizing user impact.
DevOps oriented teams spend less time on administrative support
This could be a result of better communication, higher level of automation and the availability of self-service tools and scripts for most support tasks. If there’s a high level of provisioning and automation, there’s no reason why admin support shouldn’t dwindle down to a very small time drain. It could also mean that members of DevOps oriented teams help themselves more often than expecting to be supported by the system administrator.
DevOps oriented teams work fewer days after-hours
We asked our survey takers how many days per week they work outside of normal business hours. Here’s what we learned:
|Days worked after hours||Traditional IT||DevOps Oriented|
According to these results, DevOps team members lead a more balanced life, spend more time on automation and infrastructure improvement, spend less time fighting fires, and work less hours (especially outside of normal business hours).
DevOps-related initiatives came up on top in 2012 and 2013, according to our survey. There’s a strong need for agility to respond to ever-changing and expanding market needs. Software teams are under pressure to help meet them and the chart above validates its benefits.
Rosy Stats, but hard to adopt
How we got here
IT Organizational structures – typically Dev, QA, and Ops – have come to exist for a reason. The dev team focuses on innovating and creating apps. The QA team ensures that the app behaves as intended. The operations team keeps the infrastructure running – from the apps, network, servers, shared resources to third party services. Each team requires a special set of skills in order to deliver a superior experience in a timely manner.
Today’s users increasingly rely on software and expect it to meet their constantly evolving needs 24/7, whether they’re at their desks or on their mobile devices. As a result, IT teams need to respond to change and release app updates quickly and efficiently without compromising on quality. Fail to do so, and they risk driving users to competitors or other alternatives.
However, releasing apps quickly comes with its own drawbacks. It strains functionally siloed teams and often results in software defects, delays and stress. Infrequent communication across teams further exacerbates the issue, leading to a snowball effect of finger-pointing and bad vibes.
Spurring cultural change
Both Dev and Ops teams bring a unique set of skills and experience to software development and delivery. DevOps is simply a culture that brings development and operations teams together so that through understanding each others’ perspectives and concerns, they can build and deliver resilient software products that are production ready, in a timely manner. DevOps is not NoOps. Nor is it akin to putting a Dev in Ops clothing. DevOps is synergistic, rather than cannibalistic.
DevOps is a journey
Instilling a DevOps oriented culture within your organization is not something that you embark on and chalk off as success at the end. Adopting DevOps takes discipline and initiative to bring development and operations teams together. Read up on how other organizations approach adopting DevOps as a culture and learn from their successes and failures. Put to practice what makes sense within your group. Develop a maturity model that can guide you through your journey.
The goal is to make sure that dev and ops are on the same page, working together on everything, toward a common goal: continuous delivery of working software without handoffs, hand-washing, or finger-pointing.
Support the community and the cause
Dev and Ops need to look introspectively to understand their strengths and challenges, and look for ways to contribute towards breaking down silos. Together, they should seek to educate each other, culturally evolve roles, relationships, incentives, and processes and put end user experience first.
The DevOps community is small but burgeoning, and it’s easy to find ways to get involved, like with the community-driven explosion of DevOpsDays conferences that occur around the world.
Set small goals to be awesome
Teams should collaborate to set achievable goals and milestones that can get them on the path to embracing a DevOps culture. Celebrate small successes and focus on continuous improvement. Before you know it, you will surely but gradually reap the benefits of bringing in a DevOps approach to application development and delivery.
For deeper insights into IT Ops and DevOps Productivity with a focus on people, methodologies and tools, download a 35-page report filled with stats and charts.