We’ve Urgent requirement with one of our client for Oracle Identity Manager / Developer job opening Dallas, TX

Position: Oracle Identity Manager / Developer
Duration: Full time
Location: Dallas, TX

Job Description:
• The position primarily supports the Oracle Identity Management System. The person in this position may also install, upgrade, patch, trouble shoot, and manage the web servers that deliver web content and many other enterprise level web servers.
• The position also supports web server environments that deliver web applications and business reports. The person in this position also may assist in supporting enterprise web authentication.

Minimum Experience/Education
Bachelor’s Degree in Information Technology, Computer Science, or a related discipline and three years of experience in operations analysis and design, systems programming, or a related field; or equivalent combination of training and experience.

Required Skills:
• 4 to 5 Years of OIM Experience along with Java Programming
• Oracle Identity Governance 11g
• Experience installing, managing, maintaining, patching, and upgrading Linux servers (preferably RedHat Linux).
• Knowledge of web systems.

Preferred Experience, Skills, Training/Education:
• Three or more years of working with the Linux OS and Web Technologies. Familiarity with the installation, management, maintenance, and upgrade processes for Apache content and Tomcat application servers as well as Weblogic web servers and the Oracle Identity Management System.

Thanks,
Vignesh
e mail: vignesh.renikuntla@aurionpro.com
Linkedin: http://www.linkedin.com/in/viggy1
Phone: 408-754-6161
Fax: 732 909 2221
AurionPro Solutions, Inc.
http://www.aurionpro.com

I’ve had the good fortune to have known and worked with Lori for almost 7 years and sat down with her to talk about cloud, convergence and application delivery.

Peter: First, Congratulations Lori on yet another award. If I remember correctly, this is the 2^nd year in a row that your contributions, accomplishments, and thought leadership has been recognized by CloudNOW. How’d you get so smart?

Lori: I don’t necessarily think it’s being so smart myself that’s key, it’s being afforded a platform on which smart ideas – many of which are instigated by other, very smart people – can be promoted that made that happen. I won’t say I don’t have smart ideas myself, but there’s so many talented folks in the industry that it’s more a collaborative, bouncing-off-each-other process that’s critical to coming up with ways to solve new challenges.

Peter: Public, private, hybrid. Is there a clear cloud choice or organizations or does it depend on what they are trying to accomplish? What are the advantages and pitfalls of each?

Lori: Wow, that’s at least one if not two or three blog posts right there. I think it depends on what the organization is trying to achieve and what kind of applications are critical to achieving those goals. The reality is that hybrid is going to dominate the cloud landscape by virtue of sheer necessity. There’s too many needs that can’t be met by just public or just private that require a more integrated, business-driven approach to deployments. That means hybrid is going to win, hands down.

Peter: Some in the industry believe the term ‘cloud’ is starting to get a bit cliché due to potential overuse, misuse and abuse. What do you think? Has it lost some luster?

Lori: Did it ever have luster other than as link-bait? Seriously, like any new technology market the term is overused, hyped, and abused. It means different things to different people and more confusing, to different markets. It still has power, but it is losing its status as technology darling du jour to more up and coming technology that has infrastructure bling, like SDN.

Peter: Cloud Standards. The IEEE Cloud Computing Initiative has originated two working drafts (P2301 and P2302); The Cloud Security Alliance works together to define best practices in cloud security; the Open Cloud Consortium supports the development of standards among others. First, will there ever be standards and if so, what will that provide to both customers and providers? Will standards be the final keystone for those waiting in the wings?

Lori: Standards for what? Integration? Bridging? Brokering? Cloud management? We are so far away from standardization of cloud anything at this point that we’re going to have to wait and see. When customers start demanding support for a standard X or Y or Z as table stakes for being considered as a viable provider, then we’ll start seeing real movement around those standards. So in the meantime, we’re going to continue to see each provider and vendor offering up their own “standards” and maneuvering with partnerships and support of APIs. When we start seeing accepted – even de facto – standards around cloud we’ll know it’s reached maturity.

Peter: In your opinion, what are the biggest challenges facing cloud computing? Security? Availability? The misuse of the term? Standards? Confusion?

Lori: Integration and portability. There is no such thing as “cloud security”, only network, application and data security applied in the cloud or in the data center. The biggest challenge facing cloud is that it requires a new way of looking at application deployment challenges and ultimately that trickles down to how we architect at the network, its topology. That’s a bigger challenge than simply giving up control of infrastructure; after all, we did that when we adopted managed hosting. Cloud is forcing us to rethink how we architect from the network up, and that’s harder than anything else because it’s a paradigm shift (there’s a phrase we haven’t used in a decade or so, but it’s the one that fits best – and probably better now than it did then).

Peter: You presented on two topics at Cloud Connect – ‘App Delivery in the Cloud’ and ‘Managing Hybrid Cloud’. Can you give a synopsis of each?

Lori: Let’s see. On the first one: successfully delivering applications and managing access in a cloud computing environment is about balancing control with flexibility: integrating processes and leveraging the power of standards like SAML to extend enterprise governance over cloud deployed applications while distributing control into the cloud to enable consistent control over delivery policies. Managing hybrid cloud. It’s all about integration. Integrating processes, integrating networks, integrating resources. Once you do that, the management is easy. Okay, maybe not easy but easier, which is a good thing considering the state of infrastructure integration today.

Peter: How does some of these new technologies like SDN (Software Defined Networking) and NFV (Network Function Virtualization) fit into the Cloud equation?

Lori: SDN is really about enabling elasticity for scale and flexibility in topology at the network layer. In that respect, it affords cloud a very dynamic foundation on which to deploy value-added services at the application layer that can address some of the challenges with cloud noted above with respect to thinking differently about how we deploy infrastructure services in a topologically-hampered environment. NFV continues to be of most interest to service providers, and their goal is fast, flexible, programmability in the network that enables rapid development and deployment of new services that increase ARPU by offering new value and competitive advantages. As far as cloud goes, NFV could be layered atop SDN to provide a layer of elasticity and dynamic provisioning for value added services, but right now service providers are more concerned about services than they are the core network (because they rearchitected that when IMS and similar architectures became popular).

Excellent stuff, Lori! Thanks! You can connect with and follow Lori on DevCentral or Twitter

ps

Related:

• CloudNOW Announces 2nd Annual Top 10 Women in Cloud Awards at Cloud Connect
• The Cloud Network of Women
• Is Cloud Built to Fail or Built to Scale?
• Cloud: Impact of DNS on Performance
• The Future of Hybrid Cloud
• Cloud: Commoditizing End-Users
• Working with One of Top Ten Women in the Cloud
• Interop 2012 – Application Delivery Optimization with F5′s Lori MacVittie
• VMworld2012: vCloud Ecosystem Framework with Lori MacVittie
• Lori MacVittie Interview at Cloud Connect
• "Get Your SaaS Off My Cloud" by Lori MacVittie

Connect with Peter:	Connect with F5:

USASF/IASF Worlds 2011 (Finals)
2010-2011 Season

USASF/IASF Worlds 2011 (Semi Finals)
2010-2011 Season

USASF/IASF Worlds 2011 (Semi Finals)
2010-2011 Season

USASF/IASF Worlds 2011 (Prelims)
2010-2011 Season

USASF/IASF Worlds 2011 (Prelims)
2010-2011 Season

ACCA exam tips June 2013 for F5 

• Throughput accounting
• Environmental accounting
• Sales and mixed variance
• Zero based budgeting, High low method
• Linear programming
• Performance measurement

Hilary from ARRI went through the entire offering of ARRI Pro Camera Accessories at their booth:

ARRI Camera Cage System

ARRI LMB-6 Mattebox

ARRI F5/F55 Pro Camera Accessories

ARRI C300/C500 Grip Relocator

Filmtools.tv is covering NAB 2013 with  a Canon Cinema EOS C1oo, Sennheiser EW100 Wireless Microphones, LitePanels MicroPro Light, &, most importantly, Hoodman SDHC Steel Cards for their LIFETIME WARRANTY & Rugged durability.

Check us out online at www.Filmtools.com or stop by our brick and mortar location in Burbank, CA for all of your expendables and film equipment needs!

Subscribe to our YouTube channel & Vimeo Channel,  become a fan on Facebook and follow us on Twitter, to stay up to date on all Filmtools news!

• LSBF ACCA F1
• LSBF ACCA F2
• LSBF ACCA F3
• LSBF ACCA F5
• LSBF ACCA F6
• LSBF ACCA F7
• LSBF ACCA F8
• LSBF ACCA F9
• LSBF ACCA P1
• LSBF ACCA P2
• LSBF ACCA P3
• LSBF ACCA P4
• LSBF ACCA P5
• LSBF ACCA P7

USASF/IASF Worlds 2007
2006-2007 Season

USASF Worlds 2004
2003-2004 Season

All Star Challenge Return to Atlantis 2013 (Day 2)
2012-2013 Season

All Star Challenge Return to Atlantis 2013 (Day 1)
2012-2013 Season

All Star Challenge Return to Atlantis 2013 (Day 1)
2012-2013 Season

Several analysts, such as the one in the story above, are hinting that F5′s results might be an indicator that IT spending is heading downward and they indicate that this trend might affect your bigger vendors like Juniper and Cisco.  I can’t tell you whether there is a slowdown.  But I can tell you there has been a definite shift in where those resources are going.

This trend has actually been in the works for a few years and it’s part of my job to be on top of what these vendors are offering, where they are heading, etc…  I can tell you that I’ve had serious doubts about F5′s ability to survive for a few years and I’ll tell you why.

To give a brief summary, F5 is in the position that Checkpoint was in for many years.  They were viewed as the premiere product offering in their niche category.  They had great products that no one could touch, and they charged a high premium to obtain those.  I think F5 is finding themselves in this situation now and frankly, my experience with them tells me that they haven’t reacted quickly enough to save that reputation.  In turn, this means they have lost the ability to protect those years of very nice revenue and profit.

In my previous role at a manged service provider, I was responsible for much of the networking product offerings the company sold.  Prior to 2008 when we released our first multi-tenant public cloud offering, the load balancing products were pretty cut and dry.  We offered some basic load balancer options based on BSD for customers that didn’t need all the functionality that F5 offered.  For the customers that needed that functionality, we offered F5 which at the time was viewed as the top of the line (and may still be for the time being).  The monthly recurring price difference between those two services was very high, but the customers could basically do anything they needed to do from the perspective of load balancing.

Enter cloud.  Early on in the cloud days, we were focused primarily on virtualizing the compute and storage.  The network resources were abstracted from the cloud infrastructure and there were no virtual firewalls, load balancers, etc…  So we pulled each tenant environment out of the compute layers and into the network, via per-tenant VLANs, and then offered layer 4 through 7 services upstream.

We needed the ability to contextualize and segment each tenant’s traffic while preserving precious resources on the physical hardware appliances running those services.  At the time, Cisco had ACE virtual contexts which allowed us to break an ACE load balancer up into multiple tenant contexts.  We did a test pilot that was actually pretty successful.  We could carve up resources for multiple tenants, although the number of tenants were very small at the time, but that was ok because every tenant didn’t need load balancing services and it was viewed as a premium value add.  We could even allocate a percentage of resources that tenant could use (memory, CPU, SSL transactions per second, etc.)  So it seemed like this was a very viable solution for what we needed.  We could have each tenant’s environment extended into the network through localized VLANs, and then we could extend those VLANs into virtual contexts upstream within the firewalls and load balancers (we were using Juniper VSYS within the ISG platform…similar concept).

The problem for us was not technology, because that was there.  The problem was two fold.  Operationally, we did not want to introduce another load balancer vendor into an already crowded managed networking product line.  We would have had to train staff on a new platform, complete all the product work required to release a new product, train the field on how to sell it, buy spares for each data center they were deployed in, etc…  The second issue was that Cisco was viewed as a horrible vendor choice for load balancers by many of our customers.  Even though they wouldn’t be managing them, we still had to fight the perception that we were using inferior products to what F5 was offering.  The issue here is that F5 didn’t offer the ability to do what ACE could.

So we went to F5 and asked them for similar functionality.  We explained what we were looking for.  At first, we got blank stares like “why in the world would you want this?”  Cloud was new and we were one of the first providers to introduce a multi-tenant IaaS offering.  As time went on, that tone changed to “just wait, we understand the need, and we have that functionality coming.”  We waited.  We waited some more.  Then we were told that we just had to wait for “version 10″ to come out.  That would solve these challenges.  It didn’t.  F5 had not listed to us or others in the industry explaining the needs for these multi-tenant infrastructures.

We ended up having to settle with using the F5s in a one-arm design that sat upstream and outside of the cloud environment.  This put severe limitations on the services we could offer them and we couldn’t restrict SSL TPS which is one of the most expensive licenses you will buy for the platform.  So one tenant could come in and use up 90% of the resources, but pay the same price as the other tenants not using many at all.

Today, I know F5 has adjusted some and offer some of these features.  But it came too late in my opinion and I’ll bet many providers were in similar situations as us.  I’m confident that F5 sales have gone down like the reports indicate and I’m betting they continue to slide.

Now, everything is being driven towards abstraction, even the network resources.  Convergence is not just happening at compute and storage, it’s happening everywhere.  Cisco and Juniper are very much in the game (look at the Juniper Contrail acquisition).  VMware is driving towards software defined networking with the Nicira buy.  It won’t be long before all of these vendors have offerings that reside on the hypervisor and there won’t be a need to run those services on physical appliances.

I deal with this stuff everyday.  I keep up with where the industry is trending and constantly research new offerings that may address some of these challenges.  In the past, F5 would have been right there in those discussions.  I can’t tell you the last time F5 came up when discussing these large cloud infrastructures.  Cisco and Juniper still come up because there is so much investment in them already within the legacy environments.  Vendors have come to trust them and many will look for their leadership going forward.  Vendors like F5 who had very niche offerings will continue to be marginalized and will ultimately be replaced.

So, back to the original point.  I don’t think F5′s performance is an indicator of the spending trends in the industry.  I think it symbolizes a shift in spending and those dollars that once fed F5 are being spent on other solutions.  To me, that means SELL and thankfully I did a few years back.

The urge to build a mandolin has resurfaced in 2013. This time, I am using some plans and books, and the advice of fellow woodworkers to build what is knows as  an F5  mandolin, an instrument originally designed by Lloyd Loar in the 1920′s and built by Gibson.

There are a lot of steps and processes necessary to building a musical instrument. This is the first time I have attempted to carve a top and back, creating an arched shape. The wood bending for the sides is much more complex than required for a dulcimer, with tighter curves and close tolerances. Even the headstock is very detailed. And this will be my first attempt at binding the edges.

I used a process called “hot pipe bending” to bend the wood sides. I soaked the wood in water for several hours, then used a short piece of 2 inch diameter steel pipe with a propane torch flame as a heating element inside the pipe. Gradually, the heat softens the wood and allows it to bend. I used walnut for the sides, or “rim.” The soundboard is carved from a piece of spruce I bought several years ago and which I intended to experiment with as a material for building a kayak. The blocks in the rim design – the headblock, tailblock, and points – are made from mahogany, as is the back. The neck is maple, with a rosewood veneer on the headstock, and it will get a rosewood fretboard as well.

So, here are some photos of my progress so far.

The frame that holds the rim in place after bending.

The mandolin sides, or “rim.”

The soundboard, partially carved and attached to the rim.