Apollo Global is reportedly negotiated a $3.5B price for the firm.
Which is faster, Python or Go? And by how much? This is the question I found myself asking earlier this week after troubleshooting a script that my son had written in Python to calculate prime numbers.
My son worked out a fairly simple algorithm to generate prime numbers which we tweaked slightly to optimize it (things like not bothering to check even numbers, not checking divisors that are larger than 1/3 of the number, not checking any number ending in 5, and so on). I’m not saying that this is production-ready code, nor highly optimized, but it does appear to work, which is what matters. The resulting code looks like this:
#!/usr/bin/python max = 100000 for tens in xrange(0,max,10): for ones in (1, 3, 7, 9): a = tens + ones halfmax = int(a/3) + 1 prime = True for divider in xrange (3, halfmax, 2): if a % divider == 0: # Note that it's not a prime # and break out of the testing loop prime = False break # Check if prime is true if prime == True: print(a) # Fiddle to print 2 as prime if a == 1: Continue reading
Its Weekly Show 300! Time for an update about how show is doing, our public appearances, and then some tech news on Greg s trip to IETF 96 in Berlin. The post Show 300: The IETF Is The Best We’ve Got & A Packet Pushers Update appeared first on Packet Pushers.
The post Worth Reading: Hot Commodities appeared first on 'net work.
As with many emerging technologies, there are pros and cons to SD-WAN adoption.
The Juniper documentation on log collector is a bit sparse to be honest, and once it is installed, SSHing to it doesn’t seem to produce a configuration menu any more. In order to change its config, there are some scripts, but I had to dig around for them:
[root@LOG-COLLECTOR bin]# ls adhoc.py disableExport.sh logcollectorWatchdog.py selfhealingES.py agentScript.sh elasticDiskAllocation.py logcollectorWatchdog.pyc selfhealingES.pyc agentUtilityScript.sh elasticDiskRollover.sh logcolmon.py startService.sh bashUtils.sh enableExport.sh logcolmon.pyc stopService.sh cleanZipLogs.sh generateReponse.pl lsStatisticsupdate.sh subsequentBootupdate.sh collectSystemLogs.sh getMountLocation.sh monitorPacketDrop.sh support-diagnostics.sh configureMailSetup.sh getRebootDetails.pl mountNfs.sh syslogForwardToggle.sh configureNameServer.sh getSystemInfo networkScript.sh updateEtcHosts.sh configureNode.sh getZipLogs.pl resizeFS.sh updateIndexerip.sh configureNtp.sh initConf.pl resourceMonitoring validateIpAddress.sh configureTimeZone.sh loadFirewal.sh rootWrapper whiteList.sh [root@LOG-COLLECTOR bin]#
They are in this directory:
[root@LOG-COLLECTOR bin]# pwd /opt/jnpr/bin [root@LOG-COLLECTOR bin]#
An important thing to be sure of is that log collector does not have two interfaces – it should have only eth0. If it gets an IP address on eth1, you might find that logging does not work. This is probably because it received a DHCP address on eth1, Continue reading
As discussed in prior Cross-VC NSX/multi-site blogs, Cross-VC NSX allows for NSX logical networking and security across multiple vCenter domains which may also be across multiple sites. The benefits of this capability are immediately clear in terms of workload mobility, resource pooling, central management and application of consistent security policies across vCenter domains/sites, and disaster recovery. More details on these use cases can be found in the prior Cross-VC NSX blogs listed below or in the recently published NSX-V: Multi-site Options and Cross-VC NSX Design Guide. This blog post, focuses on the ease and flexibility in terms of application of Cross-VC NSX for multi-site.
Prior Cross-VC NSX Blogs:
NSX-V: Multi-site Options and Cross-VC NSX Design Guide
Enhanced Disaster Recovery with Cross-VC NSX and SRM
Cross-VC NSX for Multi-site Solutions
In this example, vCenter, the primary NSX Manager, and the Universal Controller Cluster (UCC) is deployed at site 1. A secondary NSX Manager which is registered with the primary NSX Manager is deployed at site 2 along with its corresponding vCenter. For a quick overview on primary NSM Manager, secondary NSX Manager, and the UCC see this prior blog. For more detailed information, see the NSX-V: Multi-site Options and Cross-VC NSX Continue reading
A smart-bulb worm is possible, but Philips at least made it hard to do.