The company will sell 4.8 million shares priced between $20 and $22 per share later this month.
I have often fallen for the temptation of buying cheap instead of buying quality. This might be a saw, a drill, a lawnmower or just about anything imaginable. When I look at what professionals use I see them buying well-known and commercial grade products. For example, I wouldn’t expect to see my lawn care team buying a consumer lawnmower at Evil Big Box Store. They actually buy expensive commercial grade zero turn models that are roughly eight to ten times the cost of any mower I would consider.
My lawn care professionals mow lawns to make money, so what gives? Some might assume that these commercial grade products simply allow them to do their jobs faster. In nearly all cases, that is only half of the story. These products last much longer and hold up under the extremes of daily use. Their decks are heavy duty and the blades are less susceptible to being bent. The bottom line that these units mow faster AND they last longer. They spend less time in the shop and do the job they were purchased to do.
I find these quality issues with many consumer grade products. They’re basically cheap and disposable. The end result is Continue reading
SecureWorks, a Dell Technologies brand, saw the most growth at 33 percent.
The Kubernetes product joins the company's current support for Docker containers.
The programmable chip costs the same as fixed-function chips.
#!/bin/shEdit the cvp-api-topology.py script to Continue reading
# Install Fabric View on CloudVision Portal (CVP)
VER=`wget -qO - http://inmon.com/products/sFlow-RT/latest.txt`
wget http://www.inmon.com/products/sFlow-RT/sflow-rt-$VER.noarch.rpm
rpm --nodeps -ivh sflow-rt-$VER.noarch.rpm
/usr/local/sflow-rt/get-app.sh sflow-rt fabric-view
ln -s /cvpi/jdk/bin/java /usr/bin/java
sed -i '/^# http.hostname=/s/^# //' /usr/local/sflow-rt/conf.d/sflow-rt.conf
echo "http.html.redirect=./app/fabric-view/html/" >> /usr/local/sflow-rt/conf.d/sflow-rt.conf
cat <<EOT > /etc/nginx/conf.d/locations/sflow-rt.https.conf
location /sflow-rt/ {
auth_request /aeris/auth;
proxy_buffering off;
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Prefix /sflow-rt/;
proxy_set_header Host \$host;
proxy_pass http://localhost:8008/;
proxy_redirect ~^http://[^/]+(/.+)\$ /sflow-rt\$1;
}
EOT
systemctl restart nginx.service
firewall-cmd --zone public --add-port=6343/udp --permanent
firewall-cmd --reload
systemctl enable sflow-rt.service
systemctl start sflow-rt.service
wget http://www.inmon.com/products/sFlow-RT/cvp-eapi-topology.py
chmod +x cvp-eapi-topology.py
echo "configure and run cvp-eapi-topology.py"
Docker support follows on the heels of Mesosphere adoption of Kubernetes.
Pivotal Cloud Foundry (PCF) is the leading PaaS solution for enterprise customers today, providing a fast way to convert their ideas from conception to production. This is achieved by providing a platform to run their code in any cloud and any language taking care of all the infrastructure “stuff” for them.
From building the container image, compiling it with the required runtime , deploying it in a highly available mode and connecting it to the required services, PCF allows dev shops to concentrate on developing their code.
While the platform is providing developers with the most simplified experience conceivable, under the hood there are many moving parts that make that happen and plumbing all these parts can be complex. That’s where customers are really enjoying the power of VMware’s SDDC, and the glue between the PaaS and SDDC layers is NSX, it is the enabler that makes it all work.
In this blog post I detail some of the main uses cases customers have already deployed NSX for PCF on top of vSphere and how PCF and NSX are much better together in the real world.
The use cases customers are deploying with NSX for PCF are varied and ill Continue reading
The post Worth Reading: 10 Layers of Container Security appeared first on rule 11 reader.
The Full Stack Journey continues with guest Robert Kloosterhuis (a.k.a The Fluffy Admin), who joins Scott to discuss finding a balance between hands-on experience and broader knowledge.
The post Full Stack Journey 014: Robert Kloosterhuis appeared first on Packet Pushers.
It’s frustrating when the output to a show
command gives exactly the information needed, but in a format which is unintelligible. So it is with the Partner Port State field in the NXOS show lacp neighbor interface
command which reports the partner port state as a hexadecimal value. To help with LACP troubleshooting, here’s a quick breakdown of the port states reported on by LACP, and how they might be seen in Junos OS and NXOS.
The LACP port state (also known as the actor state) field is a single byte, each bit of which is a flag indicating a particular status. In this table, mux
(i.e. a multiplexer) refers to the logical unit which aggregates the links into a single logical transmitter/receiver.
The meaning of each bit is as follows:
Bit | Name | Meaning |
---|---|---|
0 | LACP_Activity | Device intends to transmit periodically in order to find potential members for the aggregate. This is toggled by mode active in the channel-group configuration on the member interfaces.1 = Active, 0 = Passive. |
1 | LACP_Timeout | Length of the LACP timeout. 1 = Short Timeout, 0 = Long Timeout |
2 | Aggregation | Will allow the link to be aggregated. 1 = Continue reading |
On a train this morning, I read Ivan Pepelnjak’s Twitter stream (because what else is there to do whilst relaxing with a coffee?), I came across this blog post on upgrading virtual-appliances.
Couldn’t agree more with the approach, but what about upgrading a workflow engine or orchestrator? I’ll call this entity a ‘wfeo’ just to make typing this article easier.
The perceived turmoil in undertaking this kind of an upgrade task is enough to make new born babies cry. Fear not. Any half decent wfeo contains it’s gubbins (workflows, drivers, logic, data) in a portable and logical data structure.
Taking StackStorm as an example, each integration (official parlance; ‘pack’), is arranged into a set of directories.
Within each directory are more directories with special names and a set of files like READMEs, configuration schemas and pack information. These top level directories that contain the pack, are portable between install bases of StackStorm giving us the power to easily clone installations, repair logic in case of a troubled upgrade and install logic freshly for new installations.
As with any platform, some syntax might change so always read the release notes for the platform and packs.
Ivan’s point is that you Continue reading